Skip to main content
Glama

wifi_schedule

Destructive

Set Wi-Fi off-schedules on TP-Link routers, such as disabling Wi-Fi from 23:00 to 07:00 on school nights. Add, update, enable, disable, or remove rules, with a dry run before changes apply.

Instructions

Wi-Fi off-schedule (e.g. no Wi-Fi 23:00-07:00 on school nights). action=get | enable | disable | add (rule={start 'HH:MM', end, days [sun..sat], bands [2g,5g,6g], enable}) | update (key, rule) | remove (key).

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_schedule"
  }
}

Input Schema

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

B3.4/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the agent knows this mutates state. The description adds the rule grammar (start/end times, days, bands) but says nothing about the confirm_token gate, irreversibility, or what enable/disable affects globally – context that matters for a destructive tool and is only available by reading 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two dense but front-loaded passages: a one-line purpose with example, then a compact action grammar. No filler; every token carries information about an action or its arguments.

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?

For a destructive, seven-parameter tool with a nested object and no output schema, the definition covers the write-side grammar but omits what 'get' returns, whether schedules are per-router, and how the enable/disable actions relate to the per-rule 'enable' flag. Adequate to call correctly, but not complete.

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 57%, and the description compensates by defining the nested 'rule' object's fields (start 'HH:MM', end, days [sun..sat], bands [2g,5g,6g], enable) that the schema leaves as a bare object, plus which actions require 'key'. It does not add anything for apply/reveal/router/confirm_token, but those already carry schema descriptions.

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 precisely – a Wi-Fi off-schedule with a concrete example ('no Wi-Fi 23:00-07:00 on school nights') – and the action list makes the scope of operations explicit. It does not differentiate itself from plausible siblings such as wifi_set or parental_control, so it stops 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 Guidelines2/5

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

There is no statement of when to reach for this tool rather than wifi_set or parental_control, and no mention of the dry-run/apply workflow that governs how it should actually be invoked (that only lives in the schema). The action enumeration implies the operations but gives no selection guidance.

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