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

FengSui 4G/5G Router MCP Server

Get the Router's Compatibility Report

get_device_report
Read-only

Fetch a router compatibility report with firmware, endpoint status/error codes, write-feature states, experimental write results, and owner permissions for experimental writes and endpoint probes.

Instructions

The router's compatibility report as FengSui shares it in a compatibility issue: model and firmware, which read endpoints answered (and the router's error codes), each write feature's state on this router (verified, experimental and turned on, offered, unsupported) and the recent experimental write results with their read-back (match = the router took it). Structure only: no identifier, address or value from the router. Also says whether the owner lets AI agents turn experimental writes on (set_experimental_write) and read endpoints FengSui does not use (probe_router_endpoints).

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_device_report"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior4/5

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

The readOnlyHint annotation already covers the safety profile, and the description adds useful context about the report's structure, its exclusion of identifiers, addresses, and values, and its inclusion of error codes and write-result read-backs. It does not cover freshness, pagination, or failure modes, but those gaps are minor for a zero-parameter report 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?

The description is front-loaded with the report's identity and then details its contents, with no filler. It is one long, densely nested sentence that could be easier to scan if broken into shorter clauses or a list.

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 input parameters and no output schema, the description carries the burden of explaining what the report contains, and it does so thoroughly. It could be slightly more complete by mentioning response format or data freshness, but it is otherwise sufficient for correct invocation.

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?

The tool takes no parameters, so there is no parameter semantics for the description to explain. The baseline score of 4 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?

The description names a specific resource, the router's compatibility report, and enumerates its contents: model/firmware, read endpoint results with error codes, per-feature write states, and recent experimental write results. This clearly distinguishes it from sibling tools that retrieve settings, telemetry, or SMS data.

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 implied by the phrase 'as FengSui shares it in a compatibility issue,' which suggests when the report is relevant. However, the description gives no explicit when-to-use or when-not-to-use guidance and does not name alternative tools for narrower questions.

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