Tools
Connect your agents to MCP servers and A2A agents
Tools connect your agents to MCP servers and A2A agents, so they can act in your own systems and draw on other AI agents. Use them to look up an order, create a support ticket, or hand a question to a specialist agent.
Register each MCP server or A2A agent once in Workspace > Integrations, manage which agents can reach it in Designer > Tools, and enable it on the LLM nodes that should call it.
What Are Tools
A tool is an action an LLM node can take while it works on a reply, such as searching documentation, looking up a record in your own system, or asking another agent for an answer. Each tool comes from one of these sources:
During its turn, the node reads the description of every tool it has access to, along with its own prompt, and decides whether a tool would help. It can call several tools, one after another, before it writes its reply.
How Tools Work
Tools follow a path from the Workspace down to each LLM node. You register an MCP server or A2A agent once, each agent decides which ones it can reach, and each LLM node decides which ones it calls.
Each level has its own role and its own default. Set them up in order, from the Workspace down to the node:
Register the Server or Agent
Every MCP server and A2A agent starts as an integration, registered once for the whole Workspace. Integrations are on by default, and turning one off removes it from every agent and node without deleting it.
Go to Workspace > Integrations and add an MCP Server by its URL or an A2A Agent by its Agent Card URL, both under the Tools category. Before saving, run Test connection or Fetch card to confirm it responds and to see the tools or skills it offers.
See the Integrations page for more details on how to set them up.
Choose What the Agent Can Reach
In Designer > Tools, you decide which of the Workspace's MCP servers and A2A agents this agent can reach. Everything is on by default. Turn one off to hide it from this agent and all of its nodes.
Before you rely on a server or agent, check that its status shows it's responding.
Choose What Each Node Calls
Each LLM v2 node has a Tools tab where you pick which of the agent's MCP servers and A2A agents it can call. Only those are offered to the model during the node's turn, so one node can look up orders while another only answers from the Knowledge Base.
In the node's prompt, say when each tool should be used and how to handle its results. Clear guidance keeps the model from calling a tool it doesn't need, or skipping one it does.
Supported AI Model Providers
Tools depend on the LLM plugin the node uses. Providers such as OpenAI and Azure support them; others either need a compatible endpoint or can't call tools at all. The node shows a message in its Tools tab when its provider can't use them.
OpenAI
✅
Azure
✅
OpenAI Compatible
Depends on the endpoint
Gemini
❌
Managing an Agent's Tools
The Designer > Tools page shows every MCP server and A2A agent in the Workspace from one agent's point of view. From here you can:
Check that each one is responding
See what it offers
Hide any that this agent shouldn't use
Forward the signed-in user's identity to MCP servers that need it

Expanding a row shows
The tools it exposes, with the descriptions the model reads
The skills it advertises
Status
Connected or Disconnected
Online or Offline
Identity forwarding
✅
❌
Forwarding the User's Identity
Some MCP servers need to know who the user is, or act with the user's own permissions, such as reading that user's orders. When the user is signed in, the agent can forward their tokens to the server in the header it expects. This applies to MCP servers only.
Pass access token
The user's OAuth access token
The server must act on the user's behalf
Pass ID token
The user's OIDC ID token
The server only needs to identify the user
To turn forwarding on:
Expand the MCP server
Under Forward user tokens, toggle Pass access token, Pass ID token, or both
Enter the Header name the server expects for each token, such as
X-Access-Token. The two names must differ, and reserved headers such asAuthorizationaren't allowed.Select Save Changes
Monitoring Tool Calls
Every tool call is recorded in the Observatory, so you can see what the model asked for, what came back, how long it took, and whether it failed. Each call appears as a Tool Call row in two places:
Observatory > Interaction Logs: Every tool call across all sessions. Use Search by Name with the tool's name to find its calls.
Observatory > Sessions > Chat Sessions: Open a session and select a user message to see the tool calls behind that reply, alongside the node's LLM call. The transcript also marks each call with a line such as
Called shipping-agent-5e6f7a8b (a2a) → completed, visible only in Observatory.

Select a Tool Call row to open its details. The payload shows what the model sent to the tool and what the tool returned:
tool: The tool's name. For MCP, the server's slug and the tool name joined by__; for A2A, the agent's slug.server: The MCP server's slug, ora2afor an A2A agentarguments: The input the model sent, as JSONoutput: What the tool returnedstatus: How the call ended, such ascompleted,failed, ortimeoutoutputTruncated:truewhen the output was cut before it went back to the modeltoolCallId: An ID for the call
An order lookup on an order management MCP server. The model passes the order number as a structured argument, and the server returns structured data.
A request to a shipping partner's agent. The model sends one complete message, and the agent answers in plain text.
Best Practices
Enable only what a node needs: Every tool on an enabled server is offered to the model. Fewer options mean faster, more accurate choices.
Say when to use each tool: The model picks tools from their descriptions and your prompt, so name the situations that call for each one
Send A2A agents complete requests: An A2A agent receives one message and can't see the conversation, so tell the model to include everything it needs
Test after every change: Run Test connection or Fetch card again after you change a URL or credentials
Last updated

