Tool configuration

Tools let agents retrieve external information or perform actions. You can bind existing platform tools to an agent or create custom tools through an MCP service or workflow. If a tool connects to an external platform, first configure the corresponding channel instance on the Data Platform, and then bind the channel instance to the tool.

What tools provide

  • External information: Query business systems, third-party services, or real-time data.

  • Actions: Invoke APIs or workflows for tasks such as data processing and content submission.

  • Business integration: Connect existing business systems and processes to agents.

Knowledge bases provide business information and supporting material. Skills define how to handle tasks, and tools query external systems or perform actions.

Tool types

  • Built-in tools: Provided by the platform and available for direct binding to an agent. Tools that access an external platform also require a corresponding channel instance.

  • Custom tools: Created through an MCP service or an existing platform workflow.

Configure an external platform connection

What a channel instance provides

A channel instance stores the connection and authorization settings a tool needs to access an external platform. By binding a channel instance, the tool identifies the platform and the account or application configuration to use.

The channel instance establishes the external platform connection, the tool provides the capability, and the agent uses that capability by binding the tool.

Configure a channel instance

  1. Open the channel configuration page on the Data Platform.

  2. Select the external platform to connect.

  3. Create a channel instance and enter the connection or authorization information.

  4. Complete authorization and save the channel instance.

  5. Return to tool configuration and bind the tool to the corresponding channel instance.

Configure and manage tools

Bind a tool

  1. Open the target agent’s configuration page.

  2. In the Tools section, select Add.

  3. Select the tool to use.

  4. If the tool accesses an external platform, select a configured channel instance.

  5. Confirm the selection and save the configuration.

When creating an agent, the system may recommend relevant tools based on the agent plan. Confirm a recommendation to bind it.

If no channel instance is available, first configure the corresponding channel on the Data Platform.

Manage bound tools

On the agent configuration page, you can view the bound tools, add more tools, inspect basic tool and invocation settings, or remove bindings that are no longer needed. For tools connected to external platforms, you can also view or replace the bound channel instance.

Unbinding removes only the association between the tool and the current agent. It does not delete the tool or channel instance, and it does not affect other agents that use the tool.

Create a custom tool

You can create a custom tool through an MCP service or an existing workflow. After creating the tool, bind it to the target agent.

Create through an MCP service

  1. In the tool configuration area, select New tool, and choose the MCP service option.

  2. Enter the tool name and description.

  3. Enter the MCP service address and select the transport.

  4. Test the connection and select a tool provided by the service.

  5. Confirm the tool information and complete creation.

The description helps the agent decide when to invoke the tool. The MCP service address must be a valid HTTP or HTTPS address, and the tool name must match the name provided by the MCP service.

Create from a workflow

  1. In the tool configuration area, select New tool, and choose the workflow option.

  2. Select the workflow to expose as a tool.

  3. Set the tool name and description.

  4. Configure the invocation instructions and run policy.

  5. Confirm the tool information and complete creation.

Invocation instructions describe the tool’s purpose, input requirements, and invocation method. The run policy determines whether the tool runs directly or requires user confirmation.

MCP tools connect through an MCP service address, and workflow tools invoke workflows within the platform. They generally do not require an external platform channel instance.