Skip to main content
Glama

Router Status

router_status
Read-onlyIdempotent

Retrieves router uptime in seconds plus WAN IPv4/IPv6 addresses and DNS servers, so you can verify connectivity and WAN configuration.

Instructions

Uptime (seconds), WAN IPv4/IPv6 addresses and WAN DNS servers.

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

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.1

TDQS

C2.8/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint=false, so the safety profile is covered. The description adds no behavior beyond that: it does not say whether values are live-polled or cached, how stale uptime may be, whether the router must be reachable, or what happens on failure. Worse, its content is really return-value information that the output schema already carries.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

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

It is short with no filler, but it is a sentence fragment lacking a leading verb or purpose clause, so the reader is not front-loaded with what the call does. Brevity here reflects under-specification rather than disciplined editing.

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?

Complexity is low (no parameters, output schema present, annotations cover safety), so the description does not need to explain return values or side effects. Still, it never states the operation itself or its place among the read-only siblings, leaving a gap that a single clause could close.

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 is nothing for the description to disambiguate and the baseline of 4 applies. The description correctly implies a no-argument call that returns a status snapshot.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description is a verbless noun phrase enumerating returned fields (uptime, WAN IPv4/IPv6 addresses, WAN DNS servers), not a statement of what the tool does. It does partly distinguish the tool from siblings like get_bandwidth_history or list_devices by naming the specific data surface, but an agent must infer that this is a 'read router uptime/WAN status' operation from the title alone.

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 when-to-use guidance, no mention of alternatives such as get_router_page or get_bandwidth_history, and no stated preconditions. The agent gets a data list but no signal about which question this tool answers versus the other read-only router tools.

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