githubEdit

Agent Tools

Tools extend what agents can do by connecting them to external data sources and APIs. Assign tools to agents to give them access to information and actions beyond the knowledge base.

Tool Types

API Tools

API tools let agents make HTTP requests to external services. Use them to connect agents to your internal systems, third-party APIs, or custom backends.

Plan required: Pro

Use cases:

  • Check inventory in your warehouse management system

  • Look up customer information in your CRM

  • Verify appointment availability in your scheduling system

  • Retrieve pricing from an external service

Configuration:

  • Name - A descriptive name for the tool

  • Description - Explains what the tool does (helps the agent know when to use it)

  • Endpoint URL - The HTTP endpoint to call

  • Method - GET, POST, PUT, or DELETE

  • Headers - Authentication headers and other required headers

  • Parameters - Query parameters or request body schema

When configuring API tools, provide clear descriptions of what information the API returns. This helps the agent use the tool appropriately and interpret responses correctly.

MCP Servers

MCP (Model Context Protocol) servers provide a standardized way to connect agents to external tools and data sources. MCP is an open protocol that enables secure, two-way connections between AI systems and external services.

Plan required: Pro

Use cases:

  • Connect to databases for real-time queries

  • Integrate with complex enterprise systems

  • Use pre-built MCP connectors for common services

  • Build custom integrations with full programmatic control

Configuration:

  • Server URL - The MCP server endpoint

  • Authentication - Credentials for the MCP server

  • Available tools - Select which tools from the server to enable

MCP servers can expose multiple tools through a single connection. Once connected, you can choose which of the server's tools to make available to your agents.

Sheet Search Tools

Sheet search tools let agents search through spreadsheet data you've uploaded to your knowledge base. This is useful for structured data that doesn't fit well in documents.

Plan required: All plans

Use cases:

  • Product specifications in a spreadsheet

  • Pricing tables

  • Store location data

  • FAQ databases in tabular format

Configuration: Sheet search tools are automatically available when you add CSV, Excel, or Google Sheets files to your knowledge base through the data sources configuration.

To use a spreadsheet as a searchable tool:

  1. Upload the spreadsheet via AI Settings > Knowledge Base

  2. Enable the sheet as a tool in AI Settings > Agents when configuring your agent

  3. The agent can now search and retrieve data from the spreadsheet

See Sheet Search Integration for detailed setup instructions.

Assigning Tools to Agents

Tools are assigned at the agent level. Each agent can have different tools based on its responsibilities.

To assign tools to an agent:

  1. Navigate to AI Settings > Agents

  2. Select the agent you want to configure

  3. In the Tools section, select the tools this agent should have access to

  4. Save your changes

Best Practices

Provide clear tool descriptions

Agents use tool descriptions to decide when to use each tool. Write descriptions that clearly explain:

  • What information the tool provides

  • When the tool should be used

  • What parameters the tool requires

Limit tools per agent

Only assign tools that an agent actually needs. Too many tools can confuse the agent about which tool to use for a given query.

Test tools before deployment

Verify that your API tools and MCP servers are working correctly before assigning them to production agents. Use the test feature in the tool configuration to validate responses.

Handle errors gracefully

Configure your tools to return helpful error messages. When a tool fails, the agent should be able to communicate the issue to customers appropriately.

Secure sensitive tools

API tools that access sensitive data should use appropriate authentication. Never expose credentials in tool configurations that could be visible to end users.

Last updated