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

FengSui 4G/5G Router MCP Server

Get Cellular Settings

get_cellular_settings
Read-onlyIdempotent

Reads the router's cellular settings—network mode, SIM slot and state, PIN attempts, airplane mode, roaming, operator choice, APN, and data limit—to inspect or refresh current configuration.

Instructions

Read the router's cellular settings: the network mode in use and the ones it can be set to, the SIM slots it can switch between and the one in use, the SIM card's state and PIN attempts left, airplane mode, data roaming, how the operator is chosen, the access point (APN, never its password) and the router's own data limit. A part the router does not report is null.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_cellular_settings"
  }
}

Input Schema

NameRequiredDescriptionDefault
refreshNoRead the router now instead of the last snapshot.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), so the description's job is to add context, which it does: unreported parts are returned as null, and the APN is returned without its password. Those two facts materially change how an agent should interpret the response. It stops short of describing pagination or response structure beyond the field list.

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?

Front-loaded with the verb and resource, then a single dense enumeration of returned fields, closing with the null caveat. The field list is long but each item earns its place given there is no output schema; only minor tightening is possible.

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 carries the burden of describing returns and does so field by field, plus the null convention and the APN password omission. What remains missing is how the refresh parameter interacts with the returned snapshot, though the schema covers that adequately.

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 the single refresh parameter already carries a clear description ('Read the router now instead of the last snapshot'), so the schema does the heavy lifting. The description adds nothing about refresh or the snapshot-vs-live distinction, which is the baseline-3 outcome for a fully documented schema.

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 ('Read the router's cellular settings') and then enumerates the exact data covered: network mode, SIM slots, SIM state/PIN attempts, airplane mode, roaming, operator selection, APN and data limit. That enumeration makes it distinguishable from the broader get_router_settings sibling without opening either schema.

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 by the content list — an agent can infer this is the tool for cellular-specific data, but the description never says when to prefer it over get_router_settings, nor does it state any prerequisites or exclusions. The single refresh parameter's tradeoff is documented in the schema rather than here.

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