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

FengSui 4G/5G Router MCP Server

Change Wi-Fi Multi-Link, 5 GHz Priority and the Antenna

set_wifi_and_antenna
DestructiveIdempotent

Toggle Wi-Fi multi-link (MLO) or 5 GHz priority and select internal, external, or hybrid cellular antennas. Send only changed settings; unsupported options are refused before writing.

Instructions

Turn Wi-Fi multi-link operation (MLO) or 5 GHz priority on or off, and/or choose which cellular antennas the router uses. Send only what changes; a setting this router does not have is refused before anything is sent. get_router_settings shows the current state. Wi-Fi devices may reconnect after an MLO or 5 GHz priority change.

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": {
      "confirm": "<confirm>"
    },
    "name": "set_wifi_and_antenna"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmYesMust be true: the user explicitly asked for this change.
mloEnableNoWi-Fi multi-link operation (MLO): devices that support it use several bands at once. Some older devices connect badly while it is on.
dbhoEnableNo5 GHz priority: 2.4 GHz and 5 GHz share one Wi-Fi name and devices are steered to 5 GHz. Off gives each band its own name.
antennaModeNoWhich cellular antennas to use: 'auto', 'internal', 'external', or 'hybrid' (internal and external together, only on a router that has it).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.9.5

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already flag destructiveHint=true and idempotentHint=true, and the description adds real value on top: partial-update semantics ('send only what changes'), pre-flight validation that rejects unsupported settings before anything is sent, and the user-visible impact that Wi-Fi devices may reconnect. The reconnect warning is exactly the kind of consequence an agent needs before committing a destructive change.

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?

Four short sentences, front-loaded with the capability, then update semantics, then the discovery pointer, then the disruption warning. Every sentence carries distinct information and none restates the title or schema.

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 four-parameter destructive mutation with no output schema, the description covers the essential gaps: partial updates, validation-before-send, current-state lookup, and side effects. It does not describe the response or what a post-validation failure looks like, a minor omission given the schema already documents the confirm gate.

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?

Schema coverage is 100%, so the schema carries the field-level definitions and the baseline is 3. The description adds meaning beyond it by establishing that the setting parameters are optional and should be sent selectively, and reinforces the conditional nature of antennaMode 'hybrid' (only on routers that support it).

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 specific verbs and resources: enable/disable Wi-Fi multi-link operation (MLO) or 5 GHz priority, and select cellular antenna mode. The three settings are spelled out with their acronyms expanded, so an agent can distinguish this from siblings like set_wifi_mac_filter or set_network_mode.

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?

Explicitly routes the agent to get_router_settings for the current state and explains that only changed settings should be sent. It also warns that unsupported settings are refused before transmission, which preempts a common failure mode. It stops short of stating when this tool should not be used or listing alternatives for related Wi-Fi changes.

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