Skip to main content
Glama

wifi_set

Destructive

Reads and updates TP-Link router Wi-Fi settings—including bands, SSID, password, channel, guest networks, and Smart Connect—using dry runs and confirm tokens for safe changes.

Instructions

Wi-Fi: action=get (band=2g|5g|6g|guest|guest_access|all) | set (band, settings={ssid|name, password, hidden, enable, channel, txpower, htmode, encryption, ...}; guest also takes guest_band=2g|5g|2g5g|6g|all; guest_access takes {access, isolate}) | smart_connect (enable). Turning a radio off is CRITICAL. This server's machine is wired, so it is not 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": "wifi_set"
  }
}

Input Schema

NameRequiredDescriptionDefault
bandNo
applyNofalse (default) = dry run: show the plan, diff, warnings and risk, send nothing. true = send it.
actionNoget
enableNo
revealNoShow secrets (passwords/keys) unmasked.
routerNoWhich router (see router_status 'routers'); default main.main
settingsNo
guest_bandNo
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

A3.7/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the description need not re-state that this mutates. It adds genuine context beyond them: that radio-off operations are CRITICAL, and that the server's host is wired so the caller will not be cut off by disabling a radio — a real operational safety fact an agent could not infer from the schema.

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 pipe-delimited grammar packs the action matrix into a few dense lines with the critical safety note placed last and front-loaded actions first. It is telegraphic and occasionally cryptic ('...', 'smart_connect (enable)'), but no sentence is wasted.

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 9-parameter, nested-object mutation tool with no output schema, the description covers the action matrix, the settings payload, and the main safety hazard. Minor gaps remain around the guest/guest_access distinction from wifi_extra and around return/confirmation behavior, but the essentials are present.

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 coverage is 44% and the settings object is a free-form object with no sub-schema, so the description's enumeration of settings keys (ssid|name, password, hidden, enable, channel, txpower, htmode, encryption), guest_band values, and guest_access {access, isolate} adds real meaning. It still leaves '...' and several top-level params (reveal, router, apply, confirm_token) to the schema.

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) and enumerates the three actions (get, set, smart_connect) with their operand shapes, so an agent can tell this is the Wi-Fi radio configuration tool. It does not explicitly contrast itself with siblings like wifi_extra or wifi_schedule, so it falls short of a 5.

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 implied through the per-action parameter recipes (get needs band, set needs settings, guest_access takes access/isolate), and the 'Turning a radio off is CRITICAL' note hints at a caution path. However, there is no explicit when-to-use/when-not guidance relative to wifi_extra, wifi_schedule, or wifi_set's own get vs set choice.

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