Skip to main content
Glama

mcp_remove

Unloads a named child MCP server and shuts down all of its running instances.

Instructions

卸载子 MCP 并关闭它的全部实例。

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

Input Schema

NameRequiredDescriptionDefault
nameYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It usefully discloses a significant side effect: all instances of the sub-MCP are shut down, not just one. However, it does not say whether uninstalling is irreversible, whether stored configuration or context is deleted, or what permissions are required for 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is one compact sentence with no filler, and the action and its scope are front-loaded. Its brevity borders on under-specification, but nothing in the sentence is wasteful.

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?

An output schema exists, so return values need no explanation, and there is only one parameter. For a destructive, unannotated operation, though, the definition should mention what is lost on uninstall, how the 'name' identifier is obtained, and any failure modes. It currently covers only the core effect.

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 coverage is 0%, so the schema alone does not indicate what the parameter values mean. The single parameter 'name' is only indirectly explained by '子 MCP'; the description does not clarify whether this is a server ID, a display name, or a tool prefix, or whether it needs to match the value returned by mcp_list.

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 uses a specific verb+resource phrase ('卸载子 MCP', uninstall the sub-MCP) and states the scope ('关闭它的全部实例', shut down all of its instances). This implicitly distinguishes the tool from siblings such as mcp_install and mcp_restart, though it never names an alternative.

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?

There is no guidance on when to use this tool rather than alternatives such as mcp_restart or mcp_set_context. The purpose is unambiguous enough that an agent can infer the general use case, but no conditions, prerequisites, or exclusions are stated.

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