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

FengSui 4G/5G Router MCP Server

Switch the Network Mode

set_network_mode
DestructiveIdempotent

Sets the router's cellular network mode so it attaches only to supported standards, such as 5G, 4G, 3G, or 2G. Choose a mode listed in current settings to avoid coverage loss.

Instructions

Set what the router may attach to: auto, nr_sa (5G standalone only), nr_nsa (5G with a 4G anchor), nr_lte (5G or 4G), lte (4G only), lte_tdd (4G TDD only), lte_fdd (4G FDD only), lte_wcdma (4G or 3G), wcdma (3G only) or gsm (2G only). Only a mode get_cellular_settings lists under networkMode.options is taken. A mode the area has no coverage for takes the router offline. If the WAN stays down 3 minutes afterwards, FengSui puts the earlier value back on its own.

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

Input Schema

NameRequiredDescriptionDefault
modeYesThe network mode to set; it must be one get_cellular_settings lists under networkMode.options.
confirmYesMust be true: the user explicitly asked for this change.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.9.5

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already flag destructiveHint and idempotency, but the description adds consequences an agent cannot infer: an unsupported mode takes the router offline, and if the WAN stays down for 3 minutes the previous value is automatically restored. That rollback behavior and the outage risk are exactly the operational context needed before calling a destructive tool.

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?

It is one dense paragraph that front-loads the action and value meanings before the risk warnings. The long inline enumeration is bulky, but each entry carries distinct semantic content not present in the schema, so little is wasted.

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?

Given a destructive, 2-parameter mutation with no output schema, the definition covers the valid input space, the discovery step, and failure/rollback behavior. It omits what the immediate success or error response looks like and whether connectivity drops during the switch, which are minor for this class of tool.

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 enum is already documented there, but the description adds per-value meaning the schema lacks (nr_nsa = 5G with a 4G anchor, lte_wcdma = 4G or 3G, etc.). It also reinforces the valid-option constraint tied to get_cellular_settings, though it says nothing extra about the 'confirm' flag beyond what the schema states.

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 ('Set what the router may attach to') and enumerates the full value space, so an agent immediately knows this changes the radio access technology. It also names get_cellular_settings as the authoritative source of allowed options, which separates it from sibling setters like select_operator or lock_band.

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 a clear prerequisite — only values returned by get_cellular_settings under networkMode.options are accepted — which effectively tells the agent to call the getter first. It does not state when to prefer this tool over siblings such as select_operator or lock_band, so no explicit exclusions are offered.

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