Skip to main content
Glama

delete_mcp_server

Destructive

Permanently remove an external MCP server from the agent configuration by providing its UUID, so outdated or unwanted server connections are cleared.

Instructions

Permanently remove an external MCP server from the agent configuration.

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

Input Schema

NameRequiredDescriptionDefault
mcp_server_idYesUUID of the MCP server to remove

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.2.4
    • changedInput schema / properties / mcp_server_id / description
      Previous value: -"UUID do MCP server a remover"New value: +"UUID of the MCP server to remove"
  2. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, idempotentHint=false, and openWorldHint=false, so the safety profile is largely carried by structured data. The description reinforces this with 'Permanently' and scopes the effect to 'the agent configuration', but says nothing about dependencies (e.g., whether agents referencing the server break) or cache invalidation.

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 zero filler; the destructive qualifier appears before the resource, which is exactly the ordering an agent needs.

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 one-parameter destructive tool whose annotations cover reversibility and world scope, this is nearly sufficient. A brief note on what happens to agents or caches that reference the deleted server would close the remaining gap.

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?

Only one parameter exists and schema description coverage is 100%, with the schema itself documenting 'UUID of the MCP server to remove'. The description adds no format or lookup detail beyond that, so the schema baseline of 3 applies.

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?

States a specific verb ('Permanently remove') and resource ('external MCP server from the agent configuration'), which separates it from siblings like delete_agent or delete_api_key by resource type. It stops short of explicitly naming a sibling alternative, so it lands just below the top mark.

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

Usage Guidelines3/5

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

'Permanently' implies this is not the right tool for temporary disconnection and hints that update_mcp_server or a disable path may be preferable, but no when-to-use or when-not guidance is stated outright. Usage is only implied by the adverb.

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