Skip to main content
Glama

disconnect_mcp_server

Disconnect a registered MCP server to stop it, clear its stored environment, and remove its exposed tools from the project.

Instructions

Stop and forget an MCP server registered with connect_mcp_server, including its stored environment, and remove its tools.

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": {
      "project": "<project>",
      "name": "<name>"
    },
    "name": "disconnect_mcp_server"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesServer name as shown by project_info.
projectYesInstalled project: its slug, or its id such as "github:owner/name".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does disclose the destructive scope: the server is stopped, its stored environment forgotten, and its tools removed. It does not say whether the operation is reversible, whether credentials must be re-supplied after reconnection, or what happens when the name is unknown.

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?

One sentence, front-loaded with the verb and the actions taken, with zero filler. Nothing can be removed without losing information about what gets destroyed.

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 two-parameter, no-output-schema teardown tool, the description covers the essential facts: what it deletes and which setup tool it complements. Minor gaps are failure behavior and prerequisites such as project selection, but nothing critical is missing.

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 coverage is 100%, so both parameters are already documented, including the slug/id forms for project and the reference to project_info for the server name. The description adds no additional parameter meaning beyond confirming that `name` identifies the registered server.

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 pair ("stop and forget") plus the exact resource ("an MCP server registered with connect_mcp_server") and names the sibling tool that creates such a server, letting an agent separate teardown from setup without opening a schema.

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?

The phrase "registered with connect_mcp_server" clearly implies the use case: tearing down a previously connected server. There is no explicit statement of when not to use it (e.g., to merely pause a server, or for project-level installs handled by uninstall_project), so the guidance is clear but not exhaustive.

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