Skip to main content
Glama

wifi_extra

Destructive

Pair devices via WPS, add mesh satellites, and configure Wi-Fi 7 options like MLO, OFDMA, TWT, fast roaming, and guest network limits on TP-Link routers.

Instructions

Wi-Fi extras. WPS pairing: action=wps_push (press the router's WPS button; the call stays connected and returns the outcome: success + the device's MAC, or timeout) | wps_client_pin (pin = the device's PIN) | wait (seconds, default 125) | wps_cancel | wps_status (a session the web page/button started) | wps_settings (enable) | wps_pin_enable / wps_pin_disable / wps_pin_generate / wps_pin_default. Also mlo (Wi-Fi 7 multi-link network) | ofdma | ofdma_mimo | twt | fast_roaming | advanced (beacon, DTIM, RTS, airtime fairness, zero-wait DFS...) | guest_bandwidth | guest_time | afc | afc_refresh | status. To add a mesh satellite use mesh action=pair. Main SSIDs/passwords/channels: wifi_set.

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": "wifi_extra"
  }
}

Input Schema

NameRequiredDescriptionDefault
pinNo
waitNoseconds to keep WPS open (10-300, default 125)
applyNofalse (default) = dry run: show the plan, diff, warnings and risk, send nothing. true = send it.
actionNostatus
enableNo
revealNoShow secrets (passwords/keys) unmasked.
routerNoWhich router (see router_status 'routers'); default main.main
pin_modeNo
settingsNofields to change (see the matching router_catalog form)
confirm_tokenNoRequired with apply=true for CRITICAL changes: the token from the dry run (valid 5 minutes, bound to the exact plan and current router state).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

B3.4/5.0
Behavior3/5

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

The annotations already declare destructive=true, readOnly=false, and non-idempotent, so the safety profile is partly covered. The description adds useful WPS-specific behavior: wps_push stays connected and returns success plus the device MAC or a timeout, and wait defaults to 125 seconds. It does not explain side effects, dry-run behavior, or confirm-token requirements for the many mutating actions beyond what the schema provides.

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?

The description is dense and front-loads the WPS grouping and sibling routing, then lists the remaining actions compactly. It is necessarily long because the tool has many actions, but the pipe-delimited structure keeps it readable and mostly free of filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a roughly twenty-action, ten-parameter destructive tool, the description establishes the domain, major action families, and two sibling handoffs. It still lacks per-action usage conditions and side-effect detail, and there is no output schema covering returns, so an agent lacks some context needed for safe invocation.

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?

With 60% schema description coverage, the schema already documents several parameters such as apply, confirm_token, reveal, router, settings, and wait. The description adds action-to-parameter meaning for pin, wait, and enable, but leaves pin_mode and some action-specific parameter semantics unexplained.

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 names the resource ('Wi-Fi extras') and enumerates concrete actions such as wps_push, mlo, guest_bandwidth, and status, so an agent can tell it handles secondary Wi-Fi features rather than main SSID setup. It also distinguishes itself from siblings by routing mesh pairing and main SSID changes elsewhere, though it is a broad menu of capabilities rather than one crisp verb+resource.

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?

It explicitly routes mesh satellite pairing to mesh action=pair and main SSIDs/passwords/channels to wifi_set, which are useful alternative-tool signals. However, it gives no when-to-use or when-not guidance for the roughly twenty actions inside wifi_extra, so selecting among actions is left to inference from their names.

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