Tools
Tools are executable actions that agents call during a conversation or workflow — creating a ticket, querying memory, running a diagnostic on an edge device. You manage them under Tools in the admin sidebar.
Tool catalog
Section titled “Tool catalog”The Tools page lists every tool in your organization. Use the search box to filter the list, and Create Tool to start a new one. Opening a tool takes you to the editor; each entity opens as a closeable tab.
The tool editor
Section titled “The tool editor”The editor is a node-graph canvas, the same style as the agent editor. A publication-state selector controls who can use the tool:
| State | Effect |
|---|---|
| Draft | Only admins can test it |
| Private | Only the creator can use it |
| Live | Available to everyone in the organization |
Definition
Section titled “Definition”The definition tells the agent what the tool does and when to reach for it:
- Title and Description — what the tool is.
- Call when — the situations in which an agent should invoke it.
- Prerequisites — conditions that must hold before calling.
- Limitations — what the tool cannot do.
- Side effects — changes the call makes outside the conversation.
- Arguments — the input schema, edited in a JSON-schema builder with both a visual and a code view.
Write Call when, Prerequisites, and Limitations from the agent’s perspective — the model reads them when deciding whether and how to call the tool.
Behavior
Section titled “Behavior”- Narration policy — how the agent talks about the call in chat: Natural, Brief progress phrase, or Silent.
- Requires approval — when enabled, the user must approve each invocation before it runs.
- Activity visibility — whether the call appears in the chat transcript: Visible in chat or Hidden internal activity.
Implementation types
Section titled “Implementation types”Every tool has an implementation that determines where it executes:
| Implementation | Runs | Notes |
|---|---|---|
| Native | Built into the platform | No setup; maintained by nara |
| Edge | On your edge deployments via the Organization connector | Optional Exclusive execution restricts the tool to a specific deployment |
| Agentic | Backed by a Workflow agent | The tool call executes the agent and returns its output |
Edge implementations are written in TypeScript and shipped as tool bundles through the Edge Connector CLI — see Custom tools. Agentic implementations let you compose tools from Workflow agents without leaving the platform.
Test Console
Section titled “Test Console”The editor includes a Test Console for running the tool directly:
-
Enter the call arguments as JSON, matching the tool’s argument schema.
-
For edge tools, use Select Deployment to pick which deployment executes the call. The console warns you if the selected deployment is offline.
-
Click Execute Test and inspect the result.
Available Integrations
Section titled “Available Integrations”The Available Integrations panel in the editor links to your organization’s connected providers. Some tools depend on an active integration (for example a ticketing or knowledge-base provider) — connect and manage these under Integrations.