How tools work
When a visitor asks a question that requires live data (e.g., “What’s the status of my order?”), the agent calls the appropriate tool, fetches the data, and responds with the result. Tools are called automatically based on the conversation context. You define when a tool should be used by writing a clear description.Custom tools and MCP servers are available on the Pro plan and above. Some marketplace tools are available on all plans.
Built-in tools
These tools are automatically available when configured:Knowledge search
When your agent has a vector bucket assigned, asearch_knowledge tool is automatically added. The agent calls it before answering any question about your business.
The search uses multi-query semantic search — the AI sends 2-3 short keyword queries in parallel to maximize recall from your knowledge base. Results are merged and deduplicated before being used as context.
Web search
The Web Search tool allows your agent to search the internet when knowledge base results are insufficient. Configure it from Tools & Integrations → Marketplace. You can configure tool progress messages (e.g., “Searching knowledge base…” or “Running web search…”) that are shown to visitors while the tool runs. Configure these in your agent’s Widget settings under Tool Messages.Types of tools
Marketplace tools
Pre-built integrations you can activate with a few clicks. Go to Tools & Integrations in the sidebar and click Marketplace. Currently available:Custom API tools
Build your own tools by connecting any REST API endpoint.1
Create a new tool
Go to Tools & Integrations → click New tool.
2
Configure the endpoint
Set the HTTP method (GET, POST, etc.) and the URL. Use curly braces for dynamic parameters:
3
Add authentication
Choose from: API Key (header or query), Bearer Token, or Basic Auth. Credentials are stored securely.
4
Define parameters
Add query parameters, headers, or a JSON payload. Mark parameters as required or optional.Parameters wrapped in
{{ }} are filled dynamically by the agent based on the conversation.5
Write a clear description
The description tells the agent when to use this tool. Be specific:
6
Test it
Use the Test button to send a sample request and verify the response.
MCP tools (Model Context Protocol)
Connect to external MCP servers that expose tools via the standardized MCP protocol. This is the most flexible option for complex integrations.MCP tools are available on the Business plan.
- Go to Tools & Integrations → New tool → select MCP Server
- Enter the server URL and authentication details
- InboxMate will auto-discover all available tools from the server
Tool output processing
After a tool returns data, you can configure how the agent processes it:- Response filtering — extract only the fields you need
- Transformation — rename or restructure the data
- Error handling — define fallback messages when the API fails
Best practices
- One tool per action — don’t build a Swiss army knife. Create focused tools that do one thing well.
- Clear descriptions — the agent decides which tool to call based on the description. Vague descriptions lead to wrong calls.
- Test with real data — always test your tool with realistic inputs before publishing.
- Handle errors gracefully — configure fallback messages so the agent doesn’t say “tool failed” to visitors.