Tools

Tools are actions nara takes during a conversation or a Workflow: creating a ticket, searching Knowledge, or running a diagnostic on a device. Tools and Data types are building blocks: turn on expert mode and open Building blocks under Automation in the admin console (/admin/tools).

Tool catalog

The catalog groups Tools by category: Ticket, Knowledge, Memory, Communication, Device, and Custom. The Source shows where a Tool comes from: nara Tools ship with the platform and are read-only, Tools of your organization can be changed, and a managing organization can share Tools with you. Filter by source, runtime, and tags.

New tool and opening a Tool of your organization take you to Studio.

What a Tool defines

nara reads the definition when it decides whether and how to call a Tool:

• Title and Description — what the Tool does.
• Call when — the situations in which nara calls it.
• Prerequisites and Limitations — what must hold before the call, and what the Tool cannot do.
• Side effects — what the call changes outside the conversation.
• Arguments — the input, defined by a Data type.

Behavior settings:

• Narration — how nara mentions the call in chat: natural, a brief progress phrase, or silent.
• Approval — whether a person must approve each call before it runs. On a phone call, only a verified caller can approve it by voice.
• Visibility — whether the call appears in the chat.

Where Tools run

Runtime	Runs
Built-in	Inside the nara platform.
Web app	In the nara web app.
Edge Connector	On your own devices through the Edge Connector.
Agentic	In a workflow agent from an earlier version. nara runs existing ones; new Tools are built in Studio.

See Custom tools for building your own Edge Connector Tools.

Who can use a Tool

Assistants narrow the Tools of a conversation, and a Workflow phase narrows them further. Who may use a Tool at all is set on Access Control under Tools. Some Tools need an active integration.