Skip to content

Tools

This page complements Tools in XTM One.

That guide explains what tools are for. This page gives you a quick tour of the Tools screens.

The list page

In the left navigation, this area is Tools. In standard XTM One the main visible section is Built-in Tools — platform-provided capabilities such as Image Generation, Code Interpreter, Web Fetch, Browser, and XTM One. So this page is often less about configuration and more about understanding what the platform already makes available to agents. Each card tells you whether the tool is a standard platform capability, whether it is active, and what category of action it adds.

Some platform variants also expose Custom Tools. When they do, the area behaves like the other resource libraries, gaining search, visibility and tag filters, and an Add Tool action.

Built-in tool detail pages

Opening a built-in tool leads to a detail page with Overview, Configuration, and Activity tabs.

  • Overview shows what the tool does and whether it is used in real workflows — how many agents use it, how many runs it has, and (for Image Generation) the current image model.
  • Configuration is usually informational. For Image Generation it exposes the platform-wide image model: admins can change it, non-admins can only see it — so the experience differs by role even though the page is visible to everyone.
  • Activity shows runs linked to agents using the tool.

Custom tool detail pages

When custom tools are available, their detail page has Overview, Configuration, and Activity tabs, with Test Tool and delete actions in the header.

  • Overview summarizes the tool: what it does, its language and timeout, its input parameters, and which agents use it.
  • Configuration is where you define and edit the tool. The parts that matter are durable:
    • parameters define what the tool expects
    • code (JavaScript or Python) defines what the tool does
    • a timeout defines how long the platform will wait
    • visibility and sharing settings define who can discover and reuse it

Test Tool opens a dedicated test dialog — the fastest way to validate a custom tool before binding it to an agent.

Waiting is a tool too

Some capabilities are not on the Tools page because every agent has them. wait is one: it lets an agent pause on purpose — typically after handing a long task to another agent — and re-check when the work is likely done, instead of asking for a status update over and over.

You will see it in the chat as a countdown with the agent's own explanation of what it is waiting for, next to a Continue now link:

  • Continue now ends the pause and lets the agent carry on with whatever it has.
  • The usual stop button cancels the whole response, pause included.

The agent also wakes up on its own as soon as the tasks it named have finished, so a five-minute wait often costs far less. Admins set the ceilings in Settings > General Assistant.

Read-only expectations in XTM One

In standard XTM One, built-in tools are part of the platform: visible and understandable, but not treated like personal resources. The main experience is usually inspection and understanding rather than ownership and creation.

Good habits

  • Use the tool description to understand capability before attaching it to an agent.
  • Check Agents Using before changing shared tool settings.
  • Treat Image Generation configuration as platform-wide, not per-agent.
  • In standard XTM One mode, expect built-in tools to be the main visible UX.