Skip to main content
Glama

detach_mcp_connection

Destructive

Remove an MCP server from an agent. The connection stays signed in for other agents; to sign out everywhere use delete_mcp_connection.

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": {
      "connectionId": "<connectionId>",
      "agentId": "<agentId>"
    },
    "name": "detach_mcp_connection"
  }
}

Input Schema

NameRequiredDescriptionDefault
agentIdYes
connectionIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true and idempotentHint=false, so the safety profile is covered. The description adds genuinely non-structured context: the effect is scoped to one agent and the connection remains signed in elsewhere, which clarifies the blast radius of a destructive operation.

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?

Two sentences, zero filler, with the primary action stated first and the disambiguation second. Every clause earns its place.

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?

No output schema exists, and the annotations carry the safety profile, so the description does not need to explain return values. It is nearly complete for a simple two-parameter mutation, with only parameter sourcing/format left implicit.

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

Parameters2/5

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

Schema description coverage is 0%, so both connectionId and agentId are bare strings with no guidance. The sentence structure weakly implies agentId is the agent and connectionId the connection, but there is no mention of ID format, where to obtain connection IDs (e.g. list_mcp_connections), or what happens if the pair is already detached.

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 ('Remove an MCP server from an agent') and explicitly distinguishes itself from the closely-named sibling delete_mcp_connection. An agent can tell detach from delete without inspecting either schema.

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

Usage Guidelines5/5

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

Names the alternative tool and the exact condition that selects it ('to sign out everywhere use delete_mcp_connection'), while the opening sentence establishes the default use case. The routing decision is fully specified.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources