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

FengSui 4G/5G Router MCP Server

Get the Router's Signal, Carriers and Traffic

get_cpe_telemetry
Read-onlyIdempotent

Read current 4G/5G signal, carrier aggregation, WAN status, live throughput, traffic totals, router health, and active band or cell locks to assess connection performance.

Instructions

Read the router's latest readings: the serving 4G and 5G cells with their signal (RSRP, RSRQ, SINR, RSSI), modulation, MIMO layers and transmit power, each aggregated carrier's band and bandwidth, the WAN addresses and connection state, live upload and download rates, today's and this month's traffic, the router's own status (SIM card, battery, temperatures, where it reports them), and the band and cell locks in force. Use it first to see how the connection is doing. A reading 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_cpe_telemetry"
  }
}

Input Schema

NameRequiredDescriptionDefault
refreshNotrue: read the router now, in a short session that steps aside when someone is signed in to its own web page. Omitted or false: the latest 5-second poll (read now when there is none yet).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.9.5
    • changedInput schema / properties / refresh / description
      Previous value: -"When true (or when cache is empty), triggers a polite ~150ms ephemeral CPE poll that automatically yields if a human admin is logged in."New value: +"true: read the router now, in a short session that steps aside when someone is signed in to its own web page. Omitted or false: the latest 5-second poll (read now when there is none yet)."
  2. 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 declare this read-only, idempotent and non-destructive, so the description is free to add value elsewhere. It does: "A reading the router does not report is null" sets expectations for sparse/partial results, and "latest readings" signals freshness semantics. It does not discuss the polling cadence or how the refresh session interacts with an active web login, though the input schema covers that.

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 front-loaded with the verb and the payload, and the long enumeration is justified because this tool returns many distinct telemetry families. The closing null note is short and earns its place. The middle field list is dense but not padded with filler.

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 full burden of describing returns, and it does so thoroughly across signal, carriers, WAN, rates, traffic, device status and locks. The only gap is that it does not state result units, granularity, or how the refresh path changes latency; those are minor for a read-only aggregation call.

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?

There is a single optional refresh parameter and schema description coverage is 100%, so the schema already explains the true/false/omitted behavior in detail. The description never mentions refresh or the distinction between cached poll data and an on-demand read, so it adds nothing beyond the schema. Baseline 3 applies.

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?

The description names a specific verb ("Read") and resource ("the router's latest readings") and then enumerates the concrete data returned: serving cells with RSRP/RSRQ/SINR/RSSI, carriers, WAN addresses, live rates, traffic totals, device status and band/cell locks. That is far more precise than the title alone. It stops short of explicitly distinguishing itself from near-neighbors such as get_cpe_session_status or query_telemetry_history, so it is not a 5.

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?

"Use it first to see how the connection is doing" gives a clear entry-point role and ordering, which is actionable guidance. There are no exclusions or comparison to the history/status siblings, so the agent must still infer when to prefer query_telemetry_history for past data.

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