Skip to main content
Glama

mcp_restart

Restart a specified child MCP or all child MCPs, then rebuild lazily from the latest configuration on the next call.

Instructions

重启指定子 MCP(不传 name 则重启全部),下次调用时按最新配置惰性重建。

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "mcp_restart"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It does disclose the key non-obvious behavior that the restart is not immediate but a lazy rebuild on the next call using the latest config, which is genuinely valuable. It does not say what happens to in-flight sessions, whether running state is lost, or whether permissions are required, leaving a real gap.

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 action and resource, with the scope rule in parentheses and the lazy-rebuild consequence trailing. Nothing is redundant and nothing could be trimmed without losing information.

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?

An output schema exists, so return values need not be described. For a mutation-flavored operation with no annotations, the description supplies the essential behavioral nuance (deferred rebuild) and the scope rule. It falls short only on permission/disruption details that an agent would want before triggering a restart across all MCPs.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The single parameter 'name' has 0% schema description coverage, so the schema only shows it defaults to null. The description compensates by explaining that supplying name targets one sub-MCP and omitting it targets all, which is exactly the semantic needed to use the parameter correctly. Minor gap: whether name matches an id or a display name.

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 (重启/restart) applied to a specific resource (子 MCP), and immediately qualifies the scope with the parenthetical that omitting name restarts all. That distinguishes it from siblings like mcp_install, mcp_update, or mcp_remove, though no sibling is named explicitly.

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 parenthetical '不传 name 则重启全部' implicitly tells the agent how to choose between the narrow and broad invocation, which is useful. However, there is no explicit statement of when to restart versus reload/update an MCP via mcp_update or mcp_install, so the alternative-selection guidance is only implied.

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