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

FengSui 4G/5G Router MCP Server

Search for Mobile Networks

scan_operators
Destructive

Search for nearby mobile networks, returning PLMN codes, technology, and state. Requires confirmation; scan takes up to a minute and may drop data connection.

Instructions

Search for the mobile networks in range. Takes up to a minute, and many routers drop the data connection while they search. Returns each network's code (PLMN), technology and state (current, available, forbidden). Network names are text the operators broadcast.

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

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.7/5.0
Behavior4/5

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

The description does real work beyond the annotations: it discloses that the scan can take up to a minute and that many routers drop the data connection during the scan, which is exactly the kind of context that justifies destructiveHint=true and non-idempotence. It does not say what happens if a scan fails or whether the session recovers on its own, so it stops short of fully explaining the risk.

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?

Four short sentences, each earning its place: capability, latency/side effect, return fields, and a caveat on name trustworthiness. Slight redundancy between 'takes up to a minute' and 'drop the data connection' is acceptable because they are separate warnings.

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?

With no output schema, the description correctly enumerates what comes back (PLMN, technology, state), and it covers the main operational hazard. Missing pieces are failure behavior and the rationale for the confirm parameter, but the definition is usable as written.

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?

Only one parameter (confirm) and the schema documents it at 100% coverage, so the schema carries the burden and the baseline applies. The description adds no meaning about why a read-style scan requires explicit confirmation, which is arguably the most confusing part of the contract.

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?

Opens with a specific verb and resource: 'Search for the mobile networks in range.' That is clearly distinct from selection tools like select_operator, but the description never names or contrasts a sibling, so an agent must infer the boundary itself.

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?

Usage is only implied: you scan to discover networks, presumably before selecting one. There is no explicit when-to-use statement, no exclusion, and no mention of the alternative of reading already-known cells (e.g. list_neighbor_cells) or of the confirm requirement implied by the schema.

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