Nebelus

Detach MCP server

detach_mcp_server

Destructive

Detach an MCP server from the agent.

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_id": "<agent_id>",
      "server_id": "<server_id>"
    },
    "name": "detach_mcp_server"
  }
}

Input Schema

Name	Required	Description	Default
`agent_id`	Yes	Target agent's id (from list_agents / create_agent / get_catalog view=agents).
`server_id`	Yes	Id of the attached MCP server.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedSep 14, 2026
- addedInput schema / properties / agent_id / description
```
Added value: +"Target agent's id (from list_agents / create_agent / get_catalog view=agents)."
```
- addedInput schema / properties / server_id / description
```
Added value: +"Id of the attached MCP server."
```
First observedSep 14, 2026

TDQS

B3.3/5.0

Behavior2/5

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

Annotations already mark destructiveHint=true, and the description adds no further behavioral context such as reversibility, impact on the server configuration, or whether the server remains available for re-attachment. It does not contradict the annotations, but it also does not enrich them.

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?

A single, front-loaded sentence with no filler. It conveys the action and target resource efficiently.

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

Completeness3/5

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

For a two-parameter detach operation, the description is minimally adequate, and the destructiveHint annotation covers safety. However, it lacks any mention of side effects or post-condition state, which would make it fully complete.

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?

Input schema covers both parameters with descriptions, so the baseline is 3. The tool description adds no parameter-level detail beyond what the schema already provides.

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?

Description states a specific verb ('Detach'), a specific resource ('an MCP server'), and the scope ('from the agent'). This clearly differentiates it from siblings such as attach_mcp_server and detach_ai_tool.

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

Usage Guidelines2/5

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

No explicit guidance about when to use this tool versus alternatives or prerequisites. The verb implies removal, but there is no stated inverse relationship with attach_mcp_server or warning about when not to detach.

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

All Nebelus tools Inspect

Try in Browser

Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?