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

FengSui 4G/5G Router MCP Server

Block or Restore a Wi-Fi Device

set_device_internet_access
DestructiveIdempotent

Block or unblock a specific Wi-Fi device using the router's MAC blacklist, with explicit confirmation, and check access-control status to see blocked devices.

Instructions

Cut one Wi-Fi device off the network (action 'block', through the router's Wi-Fi MAC blacklist, as the router's own device page does) or let it back on ('unblock'). FengSui refuses to block the machine it runs on. Use it only for a device the user named; get_access_control shows who is blocked.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "action": "<action>",
      "confirm": "<confirm>"
    },
    "name": "set_device_internet_access"
  }
}

Input Schema

NameRequiredDescriptionDefault
actionYes'block' cuts the device off, 'unblock' lets it back on.
confirmYesMust be true: the user explicitly asked for this change.
macAddressNoThe device's MAC address (AA:BB:CC:DD:EE:FF), as list_terminal_topology gives it.
ipv4AddressNoInstead of macAddress: the device's LAN IPv4 address, as list_terminal_topology gives it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.9.5

TDQS

A4.5/5.0
Behavior5/5

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

Beyond the annotations, the description discloses the implementation mechanism ('through the router's Wi-Fi MAC blacklist, as the router's own device page does') and an important behavioral constraint: FengSui refuses to block the machine it runs on. This adds meaningful operational context that the annotations alone do not provide.

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?

Three concise sentences front-load the core action, then add the safety constraint and usage guidance. Every sentence contributes without excess wording.

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?

Given the annotations already declare destructive and idempotent behavior, and the schema fully documents all parameters, the description provides enough context: what the tool does, the mechanism, a safety refusal, and when to use it versus get_access_control. No output schema exists, so return values do not need explanation.

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 description coverage is 100%, so the parameter meanings are already fully documented. The description restates the action values but does not add syntax or format details for macAddress, ipv4Address, or confirm beyond what the schema provides, which is appropriate at the baseline 3.

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 states a specific verb and resource: cutting one Wi-Fi device off the network or letting it back on via 'block'/'unblock'. It clearly distinguishes the tool from get_access_control by noting that get_access_control shows who is blocked, while this tool performs the block or unblock.

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?

It gives a clear usage constraint: use it only for a device the user named, and points to get_access_control for viewing blocked devices. It does not explicitly mention the sibling set_wifi_mac_filter or other possible alternatives, but the context for using this tool versus checking state is clear.

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