Create Agent Tool
Add a tool instance to an agent.
Multiple instances of the same tool_key are allowed as long as their
instance_name differs. The instance_name is the function name the LLM
will use when calling the tool, so it must be unique per agent and a
valid identifier (letters/digits/underscore/hyphen).
Documentation Index
Fetch the complete documentation index at: https://docs.mrassistant.ai/llms.txt
Use this file to discover all available pages before exploring further.
Authorizations
Bearer authentication header of the form Bearer <token>, where <token> is your auth token.
Path Parameters
Body
Schema for creating a new agent_tool instance.
The user is configuring a specific instance — a tool type (tool_key)
plus a meaningful instance_name plus per-instance config. A tool
cannot be added "raw" (just a type with no instance_name and no config)
— the controller enforces this:
- tool_key MUST exist in the registry (
tool_registrytable) - instance_name is REQUIRED (no silent default to tool_key)
- per-type required CFG fields are validated (e.g. http_webhook needs url_allowlist; send_text_tool needs provider+from_e164+secret refs)
Tool type identifier from the registry. Must match an entry from GET /agents/{agent_id}/tools/registry/available.
Stable identifier the LLM will use to call this tool. Must be meaningful (e.g. 'transfer_to_billing', 'end_call_polite'); the same tool_key can be instanced multiple times with different configs. Must be unique per agent. Pattern: ^[A-Za-z][A-Za-z0-9_-]{0,118}[A-Za-z0-9]?$
1 - 120Human-friendly UI label.
Aggregate config for a tool instance — full v2 Field Reference superset.
Frontend may submit any subset of these fields. Whatever is non-None is persisted into the agent_tool.config JSON blob. The runtime reads only the fields relevant to the resolved tool_type.
Section numbers below cite mr-assistant-tools-field-reference v2.
Response
Successful Response
Schema for tool response.