Skip to main content
Glama

router_status

Read-onlyIdempotent

Get a read-only overview of your TP-Link router: WAN/LAN addresses, internet state, Wi-Fi bands, client counts, CPU/memory, firmware, VPN switch, and extender model/mode/uplink/mesh role.

Instructions

Router overview: WAN/LAN addresses, internet state, Wi-Fi bands, client counts, CPU/memory, firmware, VPN-client switch. On an extender: model, mode, uplink, mesh role. Read-only.

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": "router_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
revealNoShow secrets (passwords/keys) unmasked.
routerNoWhich router (see router_status 'routers'); default main.main

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and the description's "Read-only" simply restates that. The genuine added value is the disclosure that the returned field set changes on an extender device. However, the description says nothing about the reveal parameter unmasking passwords/keys, which is the one behaviorally significant side effect of this 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?

Extremely tight and front-loaded: the main field list comes first, the extender variant second, the safety note last. It is telegraphic to the point of being fragmentary, but no sentence is wasted.

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 two-optional-parameter read-only overview with no output schema, the description effectively substitutes for a return-value spec by listing the fields returned and their conditional variation on extenders. The only real gap is not flagging that reveal exposes unmasked secrets.

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 100%, so both parameters (reveal, router) are already documented in the schema, including that router defaults to "main" and that values come from router_status 'routers'. The description adds no semantics beyond that, so the baseline 3 applies.

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 a specific resource and scope ("Router overview") and enumerates the content it surfaces: WAN/LAN addresses, internet state, Wi-Fi bands, client counts, CPU/memory, firmware, VPN-client switch. That is enough to distinguish it from the per-setting siblings like router_get or lan. It stops short of explicitly contrasting itself with those siblings.

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 "overview" and by the note that on an extender it returns model/mode/uplink/mesh role, which tells the agent when the result shape will differ. There is no explicit when-to-use or when-not-to-use guidance and no named alternative such as router_get or internet for narrower queries.

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