Skip to main content
Glama

attach_agent_tool

Attach an existing sn_aia_tool to a Now Assist AI agent by creating an sn_aia_agent_tool_m2m link; returns the existing link when present. Requires WRITE_ENABLED=true.

Instructions

Attach an existing tool (sn_aia_tool) to an Otto / Now Assist AI agent by creating a sn_aia_agent_tool_m2m link. Returns the existing link if one already exists. Requires WRITE_ENABLED=true.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "agent_sys_id": "<agent_sys_id>",
      "tool_sys_id": "<tool_sys_id>"
    },
    "name": "attach_agent_tool"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoLink name shown in AI Agent Studio (defaults to the tool name)
activeNoActive (default true)
inputsNoTool input definitions, e.g. [{name, description, mandatory}]
descriptionNoWhat the agent should use this tool for
tool_sys_idYessys_id of the sn_aia_tool to attach
agent_sys_idYessys_id of the sn_aia_agent
display_outputNoShow the tool output to the user
execution_modeNoautopilot = Autonomous, copilot = Supervised (default autopilot)
max_auto_executionsNoMax autonomous executions per run (default 10)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv5.0.1

TDQS

B3.4/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

The description does add value beyond the annotations by naming the prerequisite flag and the underlying link table. But 'Returns the existing link if one already exists' describes a find-or-create, no-additional-effect-on-repeat behavior, which conflicts with the supplied idempotentHint=false; the description never clarifies whether a repeat call mutates state or simply short-circuits.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences, front-loaded with the action and target, then the dedupe behavior, then the prerequisite. No filler and nothing repeated from the schema.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a nine-parameter mutation with full schema coverage, no output schema, and annotations present, the description covers the action, the prerequisite, and the return-on-duplicate case. It stops short of describing side effects on the agent's behavior or what the created link enables, which leaves a small gap.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, with every one of the nine parameters documented in the schema including the execution_mode enum. The description adds no meaning beyond that (it does not explain inputs, active, or execution_mode semantics), so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Attach an existing tool (sn_aia_tool) to an ... AI agent') and names the mechanism ('creating a sn_aia_agent_tool_m2m link'), which is far more precise than the bare tool name. It does not explicitly distinguish itself from siblings such as sn_mcp_add_tool or list_agent_tools, so an agent must infer the boundary from the 'existing tool' framing.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The prerequisite 'Requires WRITE_ENABLED=true' gives a real precondition for use, and 'existing tool' implies the tool must already exist rather than be created here. However, there is no explicit when-not guidance and no routing to alternatives such as detach_agent_tool for removal or list_agent_tools to verify an existing link.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools