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

FengSui 4G/5G Router MCP Server

Change UPnP, DMZ and Firewall Switches

set_security_switches
DestructiveIdempotent

Turn UPnP, DMZ host, firewall, IP/MAC/URL filters, and WAN ping blocking on or off, changing only specified switches. Check current state with get_router_settings first.

Instructions

Turn the router's UPnP, DMZ host, firewall, its IP, MAC and URL filters, and the WAN ping block on or off. Send only the switches to change; the others stay as they are. get_router_settings shows the current state. A DMZ host is reachable from the internet on every port, and turning the firewall off removes the filters' protection.

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

Input Schema

NameRequiredDescriptionDefault
confirmYesMust be true: the user explicitly asked for this change.
dmzEnabledNotrue forwards every incoming connection to the DMZ host (dmzIpAddress); false turns the DMZ host off.
upnpEnabledNotrue lets devices on the network open ports on the router by themselves (UPnP); false stops it.
dmzIpAddressNoThe LAN IPv4 address of the device to make the DMZ host.
firewallMainSwitchNoThe router's firewall as a whole; the filters below work only while it is on.
firewallIpFilterSwitchNoThe firewall's IP address filter.
firewallMacFilterSwitchNoThe firewall's MAC address filter (for wired and Wi-Fi devices; the Wi-Fi MAC filter is set_wifi_mac_filter).
firewallUrlFilterSwitchNoThe firewall's website (URL) filter.
firewallWanPortPingSwitchNotrue blocks ping requests from the internet; false lets the router answer them.

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 flag destructiveHint=true and idempotentHint=true, and the description goes further by explaining the actual consequences: a DMZ host is reachable from the internet on every port, and disabling the firewall removes the protection of all the filters. It also discloses the sparse-update behavior (unsent switches remain unchanged), which is behavior an agent cannot infer from the annotations alone.

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 sentences, all load-bearing: scope first, update semantics second, safety consequences last. There is no repetition of the title and no filler.

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 nine-parameter destructive mutation with no output schema, the description covers scope, partial-update behavior, the read counterpart, and the key exposure risks, which is enough to call it safely. It does not say whether changes take effect immediately or require a reboot/reconnect, which is the main remaining gap for a router-level switch tool.

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 description coverage is 100%, so the schema already defines each switch and confirm; the baseline would be 3. The description earns above baseline by stating the partial-update contract for these nine optional switches and by tying the firewall switch to the dependent filter switches ("the filters below work only while it is on" in the schema pattern), which the schema alone presents only per-property.

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?

"Turn the router's UPnP, DMZ host, firewall, its IP, MAC and URL filters, and the WAN ping block on or off" names a specific verb and an enumerated resource set, so an agent knows exactly which settings are in scope. The closing contrast with get_router_settings ("shows the current state") separates the write path from the read path.

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?

"Send only the switches to change; the others stay as they are" gives concrete partial-update usage guidance, and "get_router_settings shows the current state" routes the agent to the read sibling when it needs current values. It stops short of explicit when-not-to-use exclusions or a pointer to set_wifi_mac_filter for the separate Wi-Fi MAC filter.

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