Skip to main content

Tools Tab

The Tools tab is where you give your agent capabilities beyond conversation — looking up data in your CRM, transferring calls, booking calendar slots, calling any HTTP API.

A tool is a function the agent can decide to invoke during a call. The LLM picks tools when the conversation calls for them, the runtime executes the call, and the result is fed back to the agent for its next reply.

Two kinds of tools​

Bolti supports two categories of tools, each with its own section on the Tools tab:

1. Built-in tools​

First-party tools that ship with Bolti and don't need any setup. Examples include:

  • Transfer call — hand off the live call to a human agent or another phone number
  • End call — politely terminate the conversation
  • Schedule callback — register an outbound follow-up at a specific time

Built-in tools appear in the Built-in tools section with a name and description. Toggle the checkbox to enable a tool for this agent.

The full reference for each built-in tool — including arguments and behavior — lives under Tool Calling.

2. HTTP workspace tools​

Custom tools you (or your team) define in your workspace. Each one wraps an HTTP endpoint of yours. They appear in the HTTP workspace tools section, with their HTTP method and URL shown beneath the name.

A workspace tool has:

  • Name (what the agent calls it)
  • Description (what it does — used by the LLM to decide when to invoke it)
  • HTTP method + URL (the endpoint Bolti calls)
  • Headers, body schema, and arguments (the contract the LLM follows)
  • Optional secrets (API keys, tokens — stored encrypted, never exposed to the agent)

Workspace tools are created and managed on the Tools page in the dashboard's left nav (not on the agent's Tools tab). Once created in the workspace, they become available to assign to any agent in that workspace.

To attach a workspace tool to this agent, just check it in the list and click Save Tool Assignments.

Reusable across agents

Workspace tools are designed to be reused. Define your lookup_customer tool once, then attach it to every agent that needs it (Support, Sales, Onboarding). See Tool Calling → Workspace HTTP Tools for the full guide.

Saving tool assignments​

Tool assignments use a separate Save Tool Assignments button (top right of the Tools tab) — distinct from the global Save Changes button at the top of the Settings panel.

The flow is:

  1. Toggle checkboxes for built-in and/or workspace tools.
  2. The footer at the bottom shows the current count: "Currently assigned: N tools."
  3. Click Save Tool Assignments to apply.

Changes take effect on the next call. In-flight calls finish on their previous tool set.

How the agent picks tools​

You don't write a list of "if user says X, call tool Y". The LLM reads each tool's description and decides on its own when invoking one is appropriate. Two consequences:

  1. Descriptions matter. A tool described as "Look up customer by phone number" will be invoked when the agent has a phone number and wants customer info. A vague description ("Get customer data") will be invoked too often or not at all. Treat the description as a prompt, not a label.
  2. Goal alignment matters. If your agent's goal is "book a demo", the LLM is much more likely to invoke a book_calendar_slot tool. If the goal is vague, tool usage is erratic.

Empty state​

If no tools are configured, the tab shows:

No tools found. Create tools in the Tools page first.

Visit the Tools page in the left nav to define your first workspace tool, then come back here to assign it.

What's next​