Skip to main content
Glama

router_set_24ghz_mode

Destructive

Set the existing 20 MHz 2.4 GHz Wi-Fi mode to b/g, b/g/n, or b/g/n/ax, preserving other settings, verifying read-back, and leaving 5 GHz unchanged.

Instructions

Set the existing 20 MHz 2.4 GHz radio to b/g, b/g/n or b/g/n/ax. May briefly restart that radio. Preserve other settings and verify read-back; no 5 GHz changes.

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": {
      "mode": "<mode>",
      "confirm": "<confirm>"
    },
    "name": "router_set_24ghz_mode"
  }
}

Input Schema

NameRequiredDescriptionDefault
modeYes
confirmYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

The description adds genuinely non-obvious behavior beyond the annotations: the radio may briefly restart, other settings must be preserved, and the result should be verified by read-back. This meaningfully complements destructiveHint=true and idempotentHint=false, which alone would not tell an agent about the transient outage or the verification step. It stops short of stating failure/recovery behavior or how long the radio stays down.

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?

Roughly thirty words, front-loaded with the action and mode list, followed by the risk and constraints. No filler and no repetition of the schema.

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, non-idempotent mutation this covers the essentials: exactly what changes, the restart risk, scope boundaries, and a verification instruction. The unmentioned confirm gate and the absence of any failure or rollback context are the only notable gaps, and no output schema exists to explain return values.

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 0% schema description coverage, the description must carry the load. It does map the human-readable modes ('b/g, b/g/n, b/g/n/ax') onto the enum values ('b,g', 'b,g,n', 'b,g,n,ax'), which is useful disambiguation. But the required 'confirm' boolean (const true) is never mentioned, leaving the safety gate 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 states a specific verb and resource with exact scope: 'Set the existing 20 MHz 2.4 GHz radio to b/g, b/g/n or b/g/n/ax.' The 2.4 GHz/20 MHz qualifier naturally separates it from get_wifi or any 5 GHz work, though no sibling is 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?

Usage is implied by the narrow scope ('no 5 GHz changes', 'Preserve other settings'), and the restart warning signals a disruptive operation to schedule carefully. However, it never says when to choose this tool versus router_execute_action or router_soap_action, nor what preconditions must hold.

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