Not sure whether to use tools or sub-agents? Read Extending Airia Agent first to pick the right approach.
Add a tool
Browse available tools
The tool picker shows all tool definitions available in your tenant. Use the search box to filter by name or category.
Bind credentials (if required)
Some tools require authentication credentials (for example, a CRM integration that needs an API key). If prompted, select an existing credential from the dropdown or ask an admin to add one via Credential Management.
Enable or disable individual tools
After adding tools, you can turn individual tools on or off without removing them from the configuration. This is useful during rollout or troubleshooting.- In the Tools tab, find the tool in the Configured Tools list
- Use the toggle next to the tool name to enable or disable it
- Click Save
Tool availability changes take effect on the next user message. Active conversations are not interrupted.
Connect an MCP server
MCP (Model Context Protocol) servers expose multiple tools through a single connection. Connecting one makes all of its tools available to Airia Agent.Add an MCP server
Click Add MCP Server. Enter the server’s connection details:
- Name: A display name shown in the tool list
- URL: The MCP server endpoint
- Authentication: Select the credential to use for server authentication, if required
Review available tools
Once connected, the platform fetches the server’s tool manifest. Review the tools it exposes and enable or disable individual ones as needed.
Tool response history
The Save tool responses to history toggle controls whether the full output of each tool call is included in subsequent conversation turns for LLM context.| Setting | Behavior |
|---|---|
| Off (default) | Tool results are used to generate the immediate reply but are not stored in the conversation history passed to the model on future turns |
| On | Full tool call inputs and outputs are appended to conversation history, giving the model richer context across turns |
MCP placeholder bindings
When upgrading from an earlier version of Airia Agent to v2 or later, the Tools tab may display a Placeholder Bindings section requiring resolution before the upgrade can complete. Placeholder bindings are named slots in the new agent pipeline that must be mapped to actual MCP servers or tools in your configuration. Think of them as required connections the new version expects but that the upgrade process cannot automatically infer from your existing setup.Open the Tools tab after triggering an upgrade
If placeholder bindings exist, a warning banner appears at the top of the Tools tab.
Review each binding
The list shows each placeholder name and its expected type (MCP server or tool). Match each one to the correct resource from your configured tools and servers.
Best practices
- Start small. Add two or three high-value tools first and validate that Airia Agent uses them correctly before adding more. A large tool list can increase latency and make it harder to debug unexpected behavior.
- Use descriptive tool names. Airia Agent selects tools based on their names and descriptions. Tools with clear, specific descriptions are used more accurately.
- Credential hygiene. Use service-specific credentials rather than shared personal credentials. This makes auditing easier and limits blast radius if a credential is rotated.
- Monitor usage. Use Feeds to review which tools are being invoked and whether they are returning errors.