Skip to main content
Glama

set_wifi

Destructive

Change a Wi-Fi network's name, password, enabled state, or hidden setting. Preview changes unless confirm=true; applying drops connected devices, which must reconnect with the new password if changed.

Instructions

Change a Wi-Fi network (index from wifi_networks): name, password, on/off, hidden. Devices on it drop and must reconnect, with the new password if it changed. Without confirm=true it only shows the plan.

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": {
      "network_index": "<network_index>"
    },
    "name": "set_wifi"
  }
}

Input Schema

NameRequiredDescriptionDefault
ssidNo
hiddenNo
confirmNo
enabledNo
passwordNo
network_indexYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4.4/5.0
Behavior4/5

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

Adds substantial context beyond the annotations: devices on the network will drop and must reconnect, and with the new password if it changed — a real user-facing consequence of a destructiveHint=true call. It also discloses the default non-destructive dry-run behavior, which the annotations do not convey. It stops short of saying whether omitted fields are left untouched or whether the change is reversible.

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 short sentences, front-loaded with the action and the affected fields, then the disruptive side effect, then the confirm gate. No filler, and every clause carries information an agent needs before calling.

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 destructive mutation with no output schema, the definition covers the essential risk (clients drop, reconnect with new password) and the confirmation mechanism. The remaining gap is partial-update semantics for unspecified parameters, which an agent must guess.

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 0%, so the description carries the burden and largely does: it maps name→ssid, on/off→enabled, and covers password, hidden, network_index and confirm. What it does not clarify is the null/empty-string default semantics (e.g. whether leaving ssid="" or enabled=null means 'unchanged'), which matters for a partial-update tool with six parameters.

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 a specific verb and resource ('Change a Wi-Fi network') and immediately enumerates the mutable fields: name, password, on/off, hidden. It also pins down the required identifier ('index from wifi_networks'), which distinguishes it from sibling tools like wifi_networks (read) and set_static_ip without the agent needing to open the schema.

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?

Gives clear operational guidance: pass confirm=true to actually apply, otherwise it only shows the plan, and it points at wifi_networks as the source of the index. It lacks an explicit statement of when to prefer this over alternatives (e.g. reboot_router for connectivity fixes), but the dry-run gate and index source are the key selection cues.

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