Skip to main content
Glama

extender_set

Destructive

Configure a TP-Link range extender's LED, night LED schedule, or power schedule, or reboot it safely using dry-run previews and confirmation tokens.

Instructions

Change a range extender: action=led (enable) | led_night (enable, time_start, time_end) | power_schedule (enable) | reboot. (Extended networks / high-speed mode: read them with extender; writing them is not verified yet - use router_raw_write if needed.) No settings = show current values. Dry run first; critical changes need the confirm_token. Journaled and undoable (except reboot).

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": {
      "action": "<action>"
    },
    "name": "extender_set"
  }
}

Input Schema

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

A4.7/5.0
Behavior5/5

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

Annotations already flag destructiveHint=true, idempotentHint=false, readOnlyHint=false, and the description adds material context beyond them: the dry-run default vs apply, the 5-minute confirm_token gate for critical changes, and crucially that changes are journaled and undoable except reboot. That 'except reboot' caveat is exactly the kind of irreversibility disclosure an agent needs before a destructive call.

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?

Action list is front-loaded and each clause carries information; the parenthetical caveat about extended networks is valuable but interrupts the flow of the primary instruction. Dense but nearly every sentence earns its place.

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 7-parameter destructive writer with a nested settings object and no output schema, the description covers sequencing (dry run → confirm_token), reversibility (journaled, undo except reboot) and sibling routing. The main residual gap is the unstructured contents of 'settings' and what the dry run returns in terms of diff/warnings detail.

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 only 57% and the nested 'settings' object is opaque, but the description compensates by mapping each action to its fields (led→enable, led_night→enable/time_start/time_end, power_schedule→enable) and explaining the 'no settings = show current values' mode. It does not clarify the shape of the nested settings object or the reveal parameter, so it is strong but not complete.

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?

Names a specific verb+resource ('Change a range extender') and enumerates the four discrete actions (led, led_night, power_schedule, reboot) with the fields each implies. It also explicitly distinguishes itself from the read sibling 'extender' and from 'router_raw_write', so an agent can tell what tool it is without opening 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 Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives explicit routing: read extended networks/high-speed mode with 'extender', write them via 'router_raw_write'. Adds behavioural preconditions ('No settings = show current values', 'Dry run first; critical changes need the confirm_token'), which tells the agent the correct call sequence rather than leaving it to inference.

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