Skip to main content
Glama

sn_mcp_remove_tool

Destructive

Detach a tool from an MCP Server Console server and optionally delete its definition and inputs when unused, with safeguards for shared and out-of-box definitions; requires write access.

Instructions

Detach a tool from an MCP Server Console server. With delete_definition=true the definition and its inputs are also deleted, but only when no other server uses it and it is not an out-of-box (scoped) definition. 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": {
      "server": "<server>",
      "tool": "<tool>"
    },
    "name": "sn_mcp_remove_tool"
  }
}

Input Schema

NameRequiredDescriptionDefault
toolYesTool definition name or sys_id
serverYesServer name, label or sys_id
delete_definitionNoAlso delete the tool definition and its inputs (default false)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv5.0.1

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the bar is lower, but the description goes well beyond them: it names exactly what is destroyed (the definition and its inputs), the two conditions under which that destruction is refused, and the WRITE_ENABLED configuration gate. Those are the operational facts an agent cannot derive from the annotations.

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 sentences, front-loaded with the primary action, then the optional destructive branch, then the hard prerequisite. No restatement of the name and no filler.

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

Completeness5/5

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

For a destructive, non-idempotent mutation tool with only three fully documented parameters and no output schema, the description covers side effects, refusal conditions, and the auth/config gate. Nothing an agent needs in order to invoke it safely 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 baseline is 3; the description earns above that by attaching conditional semantics to delete_definition (multi-server and out-of-box restrictions) that the schema only labels as "(default false)". It does not explain accepted identifier forms for server/tool, but the schema already does.

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?

The description opens with a specific verb and resource ("Detach a tool from an MCP Server Console server") and immediately clarifies the distinction between detaching the association and deleting the underlying definition. That is precisely the ambiguity an agent needs resolved to choose between this and sn_mcp_add_tool-style operations.

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?

It states concrete preconditions for the destructive branch: delete_definition=true only works when no other server uses the definition and it is not out-of-box/scoped. It also flags REQUIRES WRITE_ENABLED=true. What it lacks is an explicit statement of when to prefer plain detach over detach-plus-delete, or what to do when the precondition fails.

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