Skip to main content
Glama

set_wifi_network

Idempotent

Change Wi-Fi network settings for primary, guest, or IoT networks, including on/off state, SSID, password, and security; band applies to the primary network. Confirm the preview to apply changes.

Instructions

Change a Wi-Fi network: on/off, SSID, password (8-63 chars) and/or security. band is for the primary network only (default: all bands). The password is checked by read-back but never returned. Two-phase; confirming takes 1-2 minutes.

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": "<network>"
    },
    "name": "set_wifi_network"
  }
}

Input Schema

NameRequiredDescriptionDefault
bandNo
ssidNo
confirmNo
enabledNo
networkYes
passwordNo
securityNo
expected_etagNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.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 non-read-only, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds context annotations cannot carry: the password is verified by read-back but never returned, and the operation is two-phase with a confirmation that takes 1-2 minutes. It does not explain what happens to already-connected clients when credentials 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?

Three short sentences, front-loaded with the verb and affected fields, then the band scoping rule, then the behavioral caveats. Every clause carries information an agent needs; nothing is padded.

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?

An output schema exists so return values need not be described, and annotations cover safety. The remaining gap is concurrency and confirmation semantics: expected_etag is undocumented and it is unclear whether the unconfirmed phase stages a change or applies it immediately, which matters for a mutating, idempotent tool.

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 description coverage is 0%, so the description must carry parameter meaning: it constrains the password to 8-63 characters and explains that band defaults to all bands and only applies to the primary network. It only hints at confirm via 'two-phase; confirming...' and leaves expected_etag (a concurrency/version guard) entirely unexplained, which is a real gap for an 8-parameter mutation.

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?

States a specific verb and resource ('Change a Wi-Fi network') and enumerates the editable attributes: on/off, SSID, password, security. It is distinguishable from set_wifi_radio by operating on networks rather than radios, but that sibling is never named explicitly.

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?

Gives an implicit usage rule ('band is for the primary network only') and discloses that the operation is two-phase with a 1-2 minute confirm step, which tells the agent how to sequence the call. However, it never says when to prefer this over set_wifi_radio or get_wifi_summary, and offers no when-not guidance.

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