Tool Management
Tools are executable actions that agents invoke to interact with external systems and perform work on behalf of users. Examples include creating a support ticket, querying knowledge, checking diagnostics, or sending an email.
Each tool has a name, a description, input parameters, and a result schema. Built-in tools are handled by the platform automatically. For custom tools, you choose and maintain the implementation.
Tool list view
Section titled “Tool list view”The Tools page in the admin panel displays all tools available to your organization. From this view you can:
- Browse registered tools grouped by category.
- Search or filter the catalog to find the right tool.
- Inspect a tool’s parameters, result schema, and description.
- Open a tool to attach or update its implementation.
Creating a tool
Section titled “Creating a tool”-
Navigate to Tools in the admin sidebar.
-
Select Create Tool.
-
Fill in the required fields:
- Name — unique identifier used by agents (e.g.
restart_vpn_service) - Title — human-readable display name
- Description — explains what the tool does and when the agent should use it
- Parameters — schema defining the inputs the agent must provide
- Result Schema — schema defining the structured output
- Name — unique identifier used by agents (e.g.
-
Optionally assign a category, visibility, and documentation metadata.
-
Save the tool.
-
Attach an implementation if the tool is custom.
Implementations
Section titled “Implementations”Custom tools are typically implemented in one of two ways:
- Agentic implementation — another workflow fulfills the tool contract.
- Edge implementation — code runs through an Edge Connector close to your infrastructure.
The current editor exposes these implementation choices directly. You do not need to manually manage low-level platform runtime types for built-in tools.
Tool integrations
Section titled “Tool integrations”Some tools can be linked to third-party integrations. When a binding exists, the platform provides the required connection context at execution time.
Integration bindings are managed from the tool detail page under the Integrations tab.
Assigning tools to agents
Section titled “Assigning tools to agents”Tools are made available per agent. To change access:
-
Open the agent’s configuration page.
-
Navigate to the Tools section.
-
Add or remove tools from the agent’s active tool list.
-
Save the agent configuration.
Deleting tools
Section titled “Deleting tools”To delete a custom tool, open its detail page and select Delete. Confirm the deletion when prompted. Any agents that referenced this tool will lose access immediately.
Tool fields reference
Section titled “Tool fields reference”| Field | Type | Description |
|---|---|---|
name | string | Unique identifier used in tool calls (e.g., create_ticket) |
title | string | Human-readable display name shown in the admin UI |
description | string | Purpose description that helps the agent decide when to use the tool |
group | Category | Category: TICKET, SYSTEM, KNOWLEDGE, MEMORY, COMMUNICATION, or CUSTOM |
parameters | Schema | Defines the input arguments the agent provides |
resultSchema | Schema | Defines the structured output returned to the agent |
visibility | string | Controls whether the tool is public or system (system tools are not user-facing) |