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

FengSui 4G/5G Router MCP Server

Turn Mobile Data On or Off

set_mobile_data
DestructiveIdempotent

Enable or disable a router's mobile data connection. Turning it off cuts mobile internet while keeping LAN access; it remains off until explicitly enabled again with confirmation.

Instructions

Turn the router's mobile data on (enabled: true) or off (enabled: false). While it is off the router has no internet over the mobile network, though it stays reachable on the LAN. FengSui never turns it back on on its own: it stays off until someone turns it on here or in the console. Requires confirm: true.

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

Input Schema

NameRequiredDescriptionDefault
confirmYesMust be true: the user explicitly asked for this change.
enabledYestrue turns mobile data on, false turns it off.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.9.5

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the destructive and idempotent annotations, the description discloses the key consequences: loss of mobile internet while off, continued LAN reachability, no automatic re-enable, and the confirmation requirement. These are exactly the behavioral facts an agent needs before invoking a disruptive network change.

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?

The description is front-loaded with the core action and follows with concise, relevant consequences and the confirmation requirement. Every sentence contributes operational information without repetition.

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 two-parameter mutating tool with no output schema, the definition covers purpose, side effects, persistence, reachability, and confirmation. Nothing essential for correct invocation is omitted.

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 complete, so the parameters are already documented. The description still adds useful meaning by connecting enabled=false to a concrete network outcome and reinforcing that confirm must reflect an explicit user request.

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?

The description states a specific verb and resource: turning the router's mobile data on or off, with the boolean mapping directly tied to each state. It is clearly distinct from adjacent controls such as data roaming or device internet access.

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

Usage Guidelines4/5

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

It gives clear operational context: use this to switch mobile data, note that the router remains LAN-reachable while offline, and that the change persists until explicitly reversed. It does not name alternative tools, but the usage condition is explicit enough.

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