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

FengSui 4G/5G Router MCP Server

Reconnect the Mobile Connection

reconnect_cellular
Destructive

Drops and re-establishes the router's cellular data connection without restarting it, restoring a down mobile data link after a few seconds; the WAN address may change.

Instructions

Drop and set up again the router's mobile data connection without restarting it; the internet is down for a few seconds and the WAN address may change. On a router without a reconnect command of its own, FengSui turns the connection off and on again, and always sends the turn-on, even when the session is cut short.

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": "reconnect_cellular"
  }
}

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

A3.9/5.0
Behavior5/5

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

Beyond the destructiveHint and non-idempotent annotations, it discloses consequences an agent could not otherwise know: a few seconds of downtime and a potentially changed WAN address. It also explains the fallback implementation (off/on cycling where no native reconnect command exists) and the important guarantee that the turn-on is always sent even if the session is cut short, which is exactly the kind of reliability detail that prevents misuse.

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 side effects are front-loaded in the first clause and the two sentences are dense with relevant information. The second sentence is somewhat convoluted in its fallback explanation, but nothing is wasted or redundant.

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 mutation tool with annotations and no output schema, the description covers impact, downtime, address change, and recovery behavior. Only the relationship to sibling recovery actions (reboot, operator selection, mobile data toggling) is left unaddressed.

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?

There is a single parameter with full schema description coverage ('Must be true: the user explicitly asked for this change'), so the schema carries the semantic load. The description adds no framing about the confirmation gate or when it is legitimate to set it, which is the baseline for a 100%-covered schema.

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 gives a specific verb and resource ('Drop and set up again the router's mobile data connection') and immediately distinguishes it from a full restart with 'without restarting it', which separates it from reboot_cpe. It stops short of naming a sibling explicitly, so an agent must infer the contrast rather than being told it.

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?

Use context is implied rather than stated: the 'without restarting it' phrasing suggests preferring this over a reboot when mobile data needs re-establishing, but there is no explicit when-to-use or when-not-to-use rule, and no guidance on whether set_mobile_data or select_operator should be tried first.

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