Skip to main content
Glama
FengSui 4G/5G Router MCP Server

FengSui 4G/5G Router MCP Server

Restart the Router

reboot_cpe
Destructive

Restart the router only when the user explicitly asks; all devices lose internet and local network access until it comes back online.

Instructions

Restart the router. Every device on it loses the internet and the local network until it is back, a minute or two on most routers, and FengSui reads nothing from it meanwhile. FengSui never restarts the router on its own; use this only when the user asks for a restart.

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

Input Schema

NameRequiredDescriptionDefault
confirmYesMust be true: the user explicitly asked for this change.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.9.5

TDQS

A4.9/5.0
Behavior5/5

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

Annotations already flag destructiveHint=true, idempotentHint=false and readOnlyHint=false, but the description goes further by disclosing the blast radius (every device loses internet and local network access), the expected duration (a minute or two), and the fact that no reads are possible during the outage. Those are consequences an agent cannot derive from the annotations alone.

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 sentences: action and consequences first, then the usage gate. No filler, no repetition of the title, and the most decision-relevant fact (outage scope) precedes the procedural restriction.

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

Completeness5/5

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

For a one-parameter destructive mutation with no output schema, the definition covers action, impact, downtime, safety gate, and autonomy boundaries. Nothing an agent needs before calling it is missing.

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?

Schema coverage is 100% and the single 'confirm' parameter is self-documenting, so the baseline is 3. The description adds real meaning on top by tying the gate to an explicit user request ('use this only when the user asks for a restart'), clarifying exactly what confirming asserts.

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

Purpose5/5

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

States a specific verb and resource ('Restart the router') in the first three words, and the effect sentence makes the scope unmistakable. An agent can distinguish this from sibling operations like reconnect_cellular or set_mobile_data purely on the resource being acted on.

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

Usage Guidelines5/5

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

Explicitly states both the negative condition ('FengSui never restarts the router on its own') and the positive trigger ('use this only when the user asks for a restart'). That is a direct when-to-use / when-not-to-use rule, which is exactly what a destructive tool needs.

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