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

FengSui 4G/5G Router MCP Server

List Connected Devices

list_terminal_topology
Read-onlyIdempotent

Lists connected router devices with names, MAC/IP, connection type, Wi-Fi band, link rate and remaining DHCP lease, so you can identify a device by MAC or IP before changing its internet access.

Instructions

List the devices connected to the router, wired and Wi-Fi: each one's name, MAC and IP addresses, how it is connected (cable, or the Wi-Fi band), its link rate and the DHCP lease time left, as far as the router reports them. Use it to find the device the user means, by its MAC or IP address, before changing its internet access.

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

Input Schema

NameRequiredDescriptionDefault
refreshNotrue: read the list from the router now. Omitted or false: the last list FengSui read.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.9.5
    • changedInput schema / properties / refresh / description
      Previous value: -"Refresh live HostInfo & topology from router."New value: +"true: read the list from the router now. Omitted or false: the last list FengSui read."
  2. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so safety needs no restating. The description adds genuinely new behavioral context: the returned fields per device and the hedge 'as far as the router reports them', which warns that fields may be partial or missing rather than guaranteed. It stops short of describing ordering, pagination, or behavior when no devices are listed.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, front-loaded with the verb and resource, then the return fields, then the usage rule. The field enumeration is dense but justified because there is no output schema, and every clause (including the 'as far as the router reports them' qualifier) carries information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a single-boolean-parameter list tool with no output schema, the description supplies the return shape itself and a data-completeness caveat, while annotations carry the safety profile and the schema documents refresh. Nothing an agent needs in order to select and call this correctly appears to be 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 the refresh parameter is documented with the cached-vs-live distinction already, so the description adds nothing on that axis. It never mentions re-reading the router now versus using the last stored list. Baseline 3 is appropriate when the schema carries parameter meaning in full.

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 (list) and resource (devices connected to the router), then enumerates exactly what is returned for each device: name, MAC, IP, connection type/band, link rate, DHCP lease time. The downstream tie-in ('before changing its internet access') distinguishes it from mutating siblings like set_device_internet_access.

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 an explicit workflow trigger: use it to resolve the device the user means by MAC or IP before changing its internet access. That is clear when-to-use guidance tied to a real downstream action, though it does not state any when-not-to-use or freshness caveats at the description level (those live in the refresh parameter).

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