AI Tools

Tool nodes provide capabilities that AI Agents can invoke during reasoning. Each tool defines a schema that the LLM understands and uses to decide when and how to call the tool.

How Tools Work

Connect Tool nodes to the AI Agent’s input-tools handle (diamond shape)
Agent discovers connected tools and their schemas
LLM decides when to call tools based on the user’s request
Tool executes and returns results to the agent
Agent continues reasoning with the tool’s output

[Calculator Tool] --+
                    +--(tools handle)--> [AI Agent] --> [Output]
[Web Search Tool] --+

Available Tools

Tool	Description	Use Case
Calculator	Math operations	Calculations, arithmetic
Current Time	Date/time with timezone	Scheduling, time-based logic
Web Search	Search the internet	Current information, research
Android Toolkit	Android device control	Device automation
AI Agent	Delegate to child agent	Complex sub-tasks (fire-and-forget)
Specialized Agents	Domain-specific delegation	Android, coding, web, task, social

Calculator Tool

Performs mathematical operations including basic arithmetic and advanced functions.

Operations

Operation	Description	Example
add	Addition	5 + 3 = 8
subtract	Subtraction	10 - 4 = 6
multiply	Multiplication	6 * 7 = 42
divide	Division	20 / 4 = 5
power	Exponentiation	2^8 = 256
sqrt	Square root	sqrt(16) = 4
mod	Modulo	17 % 5 = 2
abs	Absolute value	abs(-5) = 5

Parameters

toolName

string

default:"calculator"

Tool identifier shown to the LLM

toolDescription

string

Description of the tool’s capabilities for the LLM

Schema (LLM View)

{
  "operation": "add | subtract | multiply | divide | power | sqrt | mod | abs",
  "a": "number (first operand)",
  "b": "number (second operand, optional for sqrt/abs)"
}

Example Interaction

User: "What's 15% of 230?"
Agent: [Calls calculator with multiply(230, 0.15)]
       "15% of 230 is 34.5"

Current Time Tool

Gets the current date and time with timezone support.

Parameters

toolName

string

default:"currentTime"

Tool identifier shown to the LLM

toolDescription

string

Description of the tool’s capabilities

defaultTimezone

string

default:"UTC"

Default timezone (e.g., “America/New_York”, “Europe/London”, “Asia/Tokyo”)

Schema (LLM View)

{
  "timezone": "string (optional, defaults to UTC)"
}

Output

{
  "datetime": "2025-01-30T14:30:00-05:00",
  "date": "2025-01-30",
  "time": "14:30:00",
  "timezone": "America/New_York",
  "day_of_week": "Thursday",
  "unix_timestamp": 1738262000
}

Example Interaction

User: "What time is it in Tokyo?"
Agent: [Calls currentTime with timezone="Asia/Tokyo"]
       "It's currently 4:30 AM on Friday in Tokyo."

Web Search Tool

Searches the internet using DuckDuckGo (free) or Serper API (requires API key).

Parameters

toolName

string

default:"webSearch"

Tool identifier shown to the LLM

toolDescription

string

Description of the tool’s capabilities

provider

select

default:"duckduckgo"

Search provider: “duckduckgo” (free) or “serper” (API key required)

maxResults

number

default:"5"

Maximum number of search results to return

Schema (LLM View)

{
  "query": "string (search query)",
  "max_results": "number (optional, 1-10)"
}

Output

{
  "results": [
    {
      "title": "Result Title",
      "url": "https://example.com/page",
      "snippet": "Brief description of the page..."
    }
  ],
  "query": "original search query"
}

Example Interaction

User: "What are the latest developments in quantum computing?"
Agent: [Calls webSearch with query="quantum computing news 2025"]
       "Here are the latest developments in quantum computing:
        1. IBM announced a new 1000-qubit processor...
        2. Google achieved quantum error correction milestone..."

Provider Comparison

Feature	DuckDuckGo	Serper
Cost	Free	Paid (API key)
Rate Limits	Moderate	High
Result Quality	Good	Excellent
Setup	None	API key required

Android Toolkit

Gateway tool that aggregates Android service nodes for device control.

Architecture

The Android Toolkit follows the Sub-Node pattern from n8n and Toolkit pattern from LangChain:

[Battery Monitor] --+
[WiFi Automation] --+--(main input)--> [Android Toolkit] --(tools handle)--> [AI Agent]
[Location] --------+

Connected Android service nodes define what the toolkit can do. The LLM sees a single android_device tool with capabilities based on connected services.

Parameters

toolName

string

default:"android_device"

Tool identifier shown to the LLM

toolDescription

string

Description of the toolkit’s capabilities

Schema (Dynamic)

The schema is built dynamically based on connected Android service nodes:

{
  "service_id": "battery | wifi_automation | location | ...",
  "action": "status | enable | disable | get | set | ...",
  "parameters": {
    // Action-specific parameters
  }
}

Connecting Services

Add Android service nodes (Battery Monitor, WiFi Automation, etc.)
Connect them to the Android Toolkit’s main input
Connect the Toolkit to the AI Agent’s tools handle

Only connected services are available to the agent.

Tool Schema Editor

The Android Toolkit includes a schema editor for customizing how the LLM sees each service:

Select the Android Toolkit node
Open the Tool Schema Editor
Select a connected service
Customize the description, fields, and types
Save changes

Example Interaction

User: "Check the battery level and turn on WiFi if it's above 50%"
Agent: [Calls android_device with service_id="battery", action="status"]
       Battery is at 72%
       [Calls android_device with service_id="wifi_automation", action="enable"]
       "Battery is at 72%, which is above 50%. I've enabled WiFi."

Available Services

When corresponding Android service nodes are connected:

Service	Actions	Description
battery	status	Battery level, charging state, health
wifi_automation	status, enable, disable, scan	WiFi control
bluetooth_automation	status, enable, disable, paired	Bluetooth control
location	get	GPS coordinates
app_launcher	launch	Launch apps by package name
app_list	list	Installed applications
audio_automation	get, set, mute, unmute	Volume control
camera_control	info, capture	Camera operations
motion_detection	get	Accelerometer/gyroscope data
environmental_sensors	get	Temperature, humidity, light

Tool Execution Flow

When the AI Agent calls a tool:

Status broadcast - executing_tool status sent to frontend
Tool node highlighted - Shows cyan border and pulse animation
Handler executed - Backend runs the tool’s handler function
Result returned - Output sent back to the agent
Agent continues - Incorporates result into response

Tool Output in Variables

Tool outputs are available as template variables:

{{calculatorTool.result}}
{{webSearchTool.results}}
{{androidTool.output}}

Agent Delegation Tool

AI Agents and specialized agents can be connected as tools to parent agents, enabling hierarchical task delegation.

How It Works

Connect any agent to a parent agent’s input-tools handle
Parent calls delegate_to_<agent_type>(task, context)
Child spawns as background task (fire-and-forget)
Parent continues immediately without waiting

Schema

{
  "task": "string (required) - The task to delegate",
  "context": "string (optional) - Additional context"
}

Example

[AI Agent] <--tools-- [Coding Agent] <--tools-- [Python Executor]

Parent delegates: delegate_to_coding_agent(task="Write a function to parse JSON") Child agent executes independently with its own connected tools.

Use agent delegation for complex sub-tasks that don’t need immediate results.

Creating Custom Tools

To add custom tools, see the AI Tool Node Guide in the repository. Key steps:

Define node in client/src/nodeDefinitions/toolNodes.ts
Add schema in server/services/ai.py
Add handler in server/services/handlers/tools.py
Update TOOL_NODE_TYPES array

Tips

Connect only the tools the agent needs. Too many tools can confuse the LLM.

Provide clear toolDescription to help the LLM understand when to use each tool.

Use Web Search for current information not in the model’s training data.

The Android Toolkit only shows services you connect - add only what you need.

Tool nodes execute when the AI Agent calls them, not when the workflow runs. They’re passive until invoked.

AI Agents

Connect tools to AI Agent

AI Skills

Skills that use tools

Android Nodes

17 Android service nodes

Webhooks

HTTP Request node

Getting Started

Tutorials

Node Catalog

Deployment

FAQ

​AI Tools

​How Tools Work

​Available Tools

​Calculator Tool

​Operations

​Parameters

​Schema (LLM View)

​Example Interaction

​Current Time Tool

​Parameters

​Schema (LLM View)

​Output

​Example Interaction

​Web Search Tool

​Parameters

​Schema (LLM View)

​Output

​Example Interaction

​Provider Comparison

​Android Toolkit

​Architecture

​Parameters

​Schema (Dynamic)

​Connecting Services

​Tool Schema Editor

​Example Interaction

​Available Services

​Tool Execution Flow

​Tool Output in Variables

​Agent Delegation Tool

​How It Works

​Schema

​Example

​Creating Custom Tools

​Tips

​Related

AI Agents

AI Skills

Android Nodes

Webhooks

AI Tools

How Tools Work

Available Tools

Calculator Tool

Operations

Parameters

Schema (LLM View)

Example Interaction

Current Time Tool

Parameters

Schema (LLM View)

Output

Example Interaction

Web Search Tool

Parameters

Schema (LLM View)

Output

Example Interaction

Provider Comparison

Android Toolkit

Architecture

Parameters

Schema (Dynamic)

Connecting Services

Tool Schema Editor

Example Interaction

Available Services

Tool Execution Flow

Tool Output in Variables

Agent Delegation Tool

How It Works

Schema

Example

Creating Custom Tools

Tips

Related