Skip to main content
Glama

detach_agent_tool

Destructive

Detach a tool from an Otto/Now Assist AI agent by deleting or deactivating the sn_aia_agent_tool_m2m link using link_sys_id or agent_sys_id plus tool_sys_id; the tool is not deleted.

Instructions

Detach a tool from an Otto / Now Assist AI agent: deletes the sn_aia_agent_tool_m2m link (or only deactivates it with deactivate_only). Identify the link by link_sys_id, or by agent_sys_id + tool_sys_id. The tool itself is not deleted. Requires WRITE_ENABLED=true.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "detach_agent_tool"
  }
}

Input Schema

NameRequiredDescriptionDefault
link_sys_idNosys_id of the sn_aia_agent_tool_m2m record
tool_sys_idNoTool sys_id (with agent_sys_id)
agent_sys_idNoAgent sys_id (with tool_sys_id)
deactivate_onlyNoSet active=false instead of deleting the link

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv5.0.1

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already flag destructiveHint=true and readOnlyHint=false, and the description adds real value on top: what exactly is destroyed (the m2m link only), what survives (the tool record), that deactivate_only downgrades the effect to active=false, and that a write flag must be enabled. No contradiction with the declared destructive, non-readonly profile.

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 tight sentences: the action and effect first, then identification options, then the safety caveat about the tool itself and the environment precondition. No filler or restated naming.

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?

Covers identification, mutation semantics, precondition, and blast radius for a destructive, zero-required-parameter tool with no output schema. Minor gaps remain: what happens when no link matches or when multiple links match the agent+tool pair, but nothing critical for correct invocation is missing.

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

Parameters4/5

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

Schema coverage is 100%, so the per-parameter descriptions already do the heavy lifting. The description still adds the either/or identification contract (use link_sys_id, or the agent+tool pair) and restates deactivate_only's semantics, which helps an agent pick a valid parameter combination.

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

Purpose5/5

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

States a specific verb and resource: detach a tool from an AI agent by deleting the sn_aia_agent_tool_m2m link. It also names the sibling concept (attach_agent_tool via 'detach') and explicitly bounds scope with 'The tool itself is not deleted.'

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

Usage Guidelines4/5

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

Gives explicit routing between two identification modes (link_sys_id versus agent_sys_id + tool_sys_id) and offers deactivate_only as the softer alternative to deletion. It also states the WRITE_ENABLED=true precondition. It stops short of saying when to prefer deactivation over deletion, but the trigger conditions are clear.

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