Skip to main content
Glama

delete_mcp_server

Destructive

Remove an MCP server configuration and disconnect. Use when the user no longer wants that outbound connector.

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": {
      "id": "<id>"
    },
    "name": "delete_mcp_server"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the safety profile is known. The description adds that the connector is disconnected as part of the removal, which is useful beyond the annotations, but it does not say whether deletion is permanent, what happens to dependent tools/agents using the connector, or whether elevated permissions are needed.

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 short sentences, zero filler, with the action stated first and the usage trigger second. Nothing needs trimming or reordering.

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?

This is a simple one-parameter mutation with no output schema, so the description's brevity is mostly appropriate. However, for a destructive operation it should clarify irreversibility and what collateral effects the disconnect has on anything referencing the server, which it omits.

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% and the single required parameter 'id' is documented nowhere. The description never mentions the parameter, so it does not clarify whether the id is an internal server id, a name, or a slug — a meaningful gap for a destructive call where a wrong id is costly.

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

Purpose4/5

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

The description gives a specific verb and resource ('Remove an MCP server configuration') plus a second effect ('disconnect'), which distinguishes it from create_mcp_server, update_mcp_server, and connect_mcp_server. It stops short of naming a sibling explicitly, but the action is unambiguous.

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 supplies a clear trigger condition: 'Use when the user no longer wants that outbound connector.' That is a real when-to-use statement rather than an implied one. It offers no when-not guidance (e.g., disconnecting temporarily without deleting the configuration) and points to no alternative tool.

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