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

FengSui 4G/5G Router MCP Server

Get the Router's Switches

get_router_settings
Read-onlyIdempotent

Reads the router's current switches and modes, such as UPnP, DMZ, firewall, filters, NAT type, bridge mode, MLO and mobile data, so you can check state before changing anything.

Instructions

Read the router's switches and modes: UPnP, the DMZ host, the firewall and its IP, MAC and URL filters and WAN ping, the NAT type, bridge mode, Wi-Fi multi-link operation (MLO) and 5 GHz priority, the antenna mode and whether external antennas are plugged in, and mobile data. Only what this router reports is filled in. Use it to see the current state before changing any of them.

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

Input Schema

NameRequiredDescriptionDefault
refreshNotrue: read the switches from the router now. Omitted or false: the last values 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 router settings."New value: +"true: read the switches from the router now. Omitted or false: the last values FengSui read."
  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 readOnlyHint=true, idempotentHint=true and destructiveHint=false, so safety is covered. The description adds genuinely useful context beyond that: "Only what this router reports is filled in," warning that returned fields may be absent depending on model firmware — a real behavioral caveat an agent needs. It also effectively documents the return payload by enumerating the settings, compensating for the missing output schema.

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 core action, with the enumeration of settings second and the usage cue last. The long field list is informative rather than filler, though it is dense and could be trimmed for scanning without losing meaning.

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 enumeration of covered settings plus the note that only router-reported values are filled in does the job of describing the return. Read-only safety is handled by annotations. Minor gap: caching behavior of the refresh parameter is only explained in the schema, not the description.

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?

The single parameter has full schema description coverage, including the omitted/false default, so the schema already carries the semantics. The prose description never mentions the refresh argument or its caching trade-off, adding no meaning beyond what the schema provides — the baseline 3 for 100% coverage.

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 opens with a specific verb and resource ("Read the router's switches and modes") and then enumerates the exact settings covered — UPnP, DMZ host, firewall/filters, NAT type, bridge mode, MLO, antenna mode, mobile data. An agent can tell this is a read-all-configuration tool rather than a targeted one. It stops short of explicitly naming a sibling reader to contrast with, which keeps it at 4 rather than 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?

The closing sentence gives a clear usage condition: "Use it to see the current state before changing any of them," which positions it as the read step preceding the setter tools. There are no explicit exclusions (e.g., when to prefer get_cellular_settings or get_access_control instead), so the guidance is clear but not exhaustive.

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