Skip to main content
Glama

router_status

Read-onlyIdempotent

Retrieve router model, firmware, internet connection status, external IP, uptime, LAN address, active Wi-Fi networks, and count of online devices in one call.

Instructions

Overview: model and firmware, internet connection (status, external IP, uptime), LAN address, Wi-Fi networks that are on, number of devices online.

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

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already establish the safe-read profile (readOnlyHint=true, idempotentHint=true), so the bar is lowered. The description still adds behavior worth knowing: it says the Wi-Fi section lists only networks that are on and that the device figure is a count of online devices, which tells the agent the data is a point-in-time live snapshot rather than a full configuration dump. It stops short of describing freshness, error behavior, or completeness guarantees.

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?

A single telegraphic sentence led by 'Overview:', with each returned field listed compactly; no filler or repetition. It is slightly clipped as prose (no verb, trailing list), but every clause earns its place by naming a distinct data point.

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?

This is a parameterless read tool with no output schema, so the description is the only place return semantics can live — and it does enumerate the expected fields. Given the annotations carry the safety profile, the definition is largely sufficient; only freshness/refresh semantics are unstated.

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?

The tool takes zero parameters, so there are no parameter semantics to explain and the baseline of 4 applies. Nothing in the description conflicts with the empty schema.

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 enumerates concrete resources: model/firmware, internet connection status with external IP and uptime, LAN address, active Wi-Fi networks, and online device count. That is enough to identify it as a read-only snapshot/overview tool, but it never states a verb ('get/return current router state') and does not distinguish it from overlapping-looking siblings such as ipv6_status or router_read.

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?

'Overview:' hints at a first-stop summary, but there is no explicit when-to-use guidance, no exclusions, and no named alternative. An agent cannot tell from the text whether router_status should be called before ipv6_status, router_read, or list_clients for a given question, so it must infer usage from the field list alone.

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