Tools are how your Toqan Agent interacts with the outside world. They let the Agent do things it otherwise couldn’t, like summarising large files, running calculations, or creating a Jira ticket on your behalf.
There are two categories: built-in tools (available via the API) and custom tools (connections you configure yourself).
Built-in tools
The following tools are available out of the box via the API:
| Tool | What it does |
|---|---|
url_resolver | Retrieves full content from a given URL |
web_search | Searches the web via Google Custom Search |
transcription | Transcribes audio and video files to text |
code_executor | Executes code for math, data analysis, and more |
text_to_image | Generates an image from a text prompt |
ocr | Extracts text from images |
summarization | Summarises documents (PDF, DOCX, articles, etc.) |
question_answering | Answers questions based on text files |
translation | Translates full text files |
Custom tools
Custom tools let you connect your Agent to systems not covered by the built-in set, Google Drive, GitHub, Confluence, Jira, or your own internal APIs. You can add up to 10 custom tools per Agent.
Setting up a custom tool
- Open the Tools tab in your Toqan Space
- Click Create custom tool
- Fill in the form using the field guide below
Custom tool fields explained
Display name
A human-readable name visible to you and your team, not visible to the Agent. Make it descriptive. Example: Create Jira Ticket.
Function name
The name the Agent sees and uses. Must be lowercase with underscores, no special characters, and unique. Example: create_jira_ticket.
Parameters Parameters are the inputs the Agent fills in when calling the tool. Each parameter has:
- Name, what the Agent should fill in (e.g.,
query,summary) - Description, extra context to help the Agent use it correctly (e.g., “This is the summary of the new ticket”)
You can reference parameters elsewhere in your tool config using $(parameter_name).
Description
A short explanation of what the tool does and what the Agent should expect as output. Example for web_search: “Performs a search on the web using Google Custom Search to retrieve structured data or summaries based on specific queries.”
Instructions
Additional guidance on when and how to use the tool. Example for web_search:
- Break down complex queries into smaller parts
- Start with an exploratory search to better understand the request
Headers Used for API configuration. Authentication is currently handled through headers only, OAuth support is coming.
Whitelisting tool call IPs
If your internal systems require IP whitelisting, allow the following addresses:
18.202.206.254
52.31.67.186
34.253.128.27
Testing your custom tool
The best way to test a custom tool is to open the Agent’s chat and send a message that should trigger it. Dedicated testing tooling is on the roadmap.