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

FengSui 4G/5G Router MCP Server

Choose the Mobile Network Operator

select_operator
DestructiveIdempotent

Lock the router to a specific mobile operator using a PLMN code and optional technology, or switch it back to automatic selection; reverts the previous setting if WAN stays down for 3 minutes.

Instructions

Keep the router on one operator's network (mode "manual" with the plmn code from scan_operators, optionally the technology), or hand the choice back to the router (mode "auto"). A network that does not accept the SIM card leaves the router without service. 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": "select_operator"
  }
}

Input Schema

NameRequiredDescriptionDefault
ratNoThe technology to register on (manual only, optional).
modeYes'manual' keeps the router on the operator in plmn; 'auto' lets the router choose.
plmnNoThe operator's code (MCC + MNC digits, e.g. 27201), as scan_operators gives it (manual only).
confirmYesMust be true: the user explicitly asked for this change.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.9.5

TDQS

A4.3/5.0
Behavior5/5

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

Annotations already flag destructiveHint=true and idempotentHint=true; the description adds exactly the context annotations cannot express — that selecting an incompatible operator can drop service entirely, and that FengSui self-reverts to the earlier value if the WAN stays down for 3 minutes. That gives the agent a concrete failure mode and a safety net to communicate.

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?

Two tightly written sentences, front-loaded with the primary action and followed by the consequence and rollback. Little waste, though the manual/auto restatement partially duplicates what the schema already says.

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 destructive, idempotent mutation with no output schema, the definition covers the action, the prerequisite source of plmn, the main failure mode, and automatic reversal. It could go slightly further by telling the agent how to verify the result afterwards (e.g. re-check session status), but nothing essential for correct invocation is missing.

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?

Schema coverage is 100% and already documents mode, plmn (MCC+MNC, max 6), rat (enum, manual-only, optional) and the confirm gate. The description restates the manual/auto semantics and the scan_operators provenance of plmn without adding format or validation detail beyond the schema, so baseline 3 applies.

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+resource: pinning the router to one operator (mode "manual" with a plmn) versus returning selection to the router (mode "auto"). The two modes are distinguished in operational terms, and the dependency on scan_operators for the plmn code is named, so an agent can tell this apart from set_network_mode 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?

Gives clear context: use manual with a plmn from scan_operators when the user wants a specific operator, use auto to hand control back. It also states the risk condition (a network that rejects the SIM leaves the router without service) and the automatic rollback. It stops short of naming exclusion cases against siblings like set_network_mode or reconnect_cellular, so it is clear but not fully routing.

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