Skip to main content
Glama

mcp_update

Update a child MCP configuration; changes automatically restart that MCP's existing instance to apply them.

Instructions

修改子 MCP 配置;改动会自动重启该 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_update"
  }
}

Input Schema

NameRequiredDescriptionDefault
cwdNo
envNo
argsNo
nameYes
commandNo
db_fileNo
enabledNo
requiredNo
strategyNo
descriptionNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full disclosure burden, and it does add one genuinely important behavior: edits automatically restart the existing instance of that MCP, which signals a disruptive side effect. Beyond that, it is silent on whether unspecified fields are preserved or cleared, what permissions are required, and whether the restart can interrupt in-flight calls.

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 two tight clauses, and the restart consequence is stated up front without filler. It is efficient, though for a 10-parameter mutation tool this brevity shades into under-specification rather than pure economy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given a mutation tool with 10 undocumented parameters, no annotations, and an automatic restart side effect, the description is far too thin for an agent to call it safely. An output schema exists, so return values need not be explained, but the update semantics and the restart's scope remain unaddressed.

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% across 10 parameters, so the description must compensate, yet it adds no meaning at all for parameters such as cwd, env, args, command, enabled, required, strategy, or db_file. It doesn't even clarify that name identifies the target MCP while the remaining fields are optional overrides, leaving null-vs-omit semantics entirely ambiguous.

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 (修改, modify) on a specific resource (子 MCP 配置, child MCP configuration), so an agent can tell it is a config-editing tool rather than an installer or invoker. However, it doesn't explicitly contrast itself with siblings such as mcp_install or mcp_restart, leaving the boundary implicit.

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?

The description implies this tool should be used to change existing child MCP settings, but it never states when not to use it (for example, for creating a new MCP, or for merely restarting one) or names the alternative tools. An agent must infer the selection rule from the sibling list.

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