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

FengSui 4G/5G Router MCP Server

Get Wi-Fi Access Control and Internet Time Rules

get_access_control
Read-onlyIdempotent

Read the router's Wi-Fi MAC filter mode, blacklist/whitelist entries, and per-device parental-control online windows to audit access rules and see when devices are blocked.

Instructions

Read the router's Wi-Fi MAC filter (off / blacklist / whitelist, both lists, capacity) and its parental-control internet time rules (allowed online windows per device; outside them the device is cut off).

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

Input Schema

NameRequiredDescriptionDefault
refreshNoRead the router now instead of the cached snapshot.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already establish readOnly/idempotent/non-destructive, so the safety profile is covered. The description adds genuine domain semantics beyond that: the filter's three modes, that both lists and capacity are returned, and that devices are cut off outside their allowed windows — meaning the agent understands the effect of what it reads.

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?

A single sentence, front-loaded with the primary resource, using compact parentheticals to disambiguate modes and the meaning of time-window violations. No filler or redundant restatement of the title.

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?

For a read-only tool with one optional parameter and no output schema, the description covers both returned structures and their semantics well enough to act on. What is missing is minor: no indication of response shape or whether the two datasets are returned together.

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?

Only one optional boolean parameter (refresh) and the schema already documents it at 100% coverage, including the cached-vs-live distinction. The description adds no further information about it, so the baseline of 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?

Specific verb ('Read') tied to two concretely named resources: the Wi-Fi MAC filter (with its off/blacklist/whitelist modes, both lists, and capacity) and parental-control internet time rules. This is far more specific than a generic settings read, though it never explicitly contrasts itself with siblings like get_router_settings.

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 read framing; there is no statement of when to prefer this over get_router_settings or other configuration readers, and no prerequisites or exclusions. An agent can infer it is the access-control read, but nothing routes it explicitly.

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