Skip to main content
Glama

router_get_wifi

Read-onlyIdempotent

Read Wi-Fi radio settings, SSID status, and connected clients without starting a radio scan, so you can inspect the router's current wireless state.

Instructions

Read radio settings, SSID status and associated clients. Does not start a radio scan.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so safety is covered. The description adds meaningful non-obvious context: the call is passive and does not trigger a radio scan, which is precisely the side effect an agent might otherwise assume from a 'get wifi' call. It does not say whether values are cached or how fresh they are.

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 sentences, both earning their place: the first front-loads what is returned, the second removes the most likely false assumption. No filler, no restatement of the tool name.

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 zero-parameter read with full annotation coverage and no output schema, the description is nearly sufficient — it enumerates the three data groups returned and rules out an active scan. The only gap is the lack of disambiguation from router_read and router_soap_read, which an agent would still have to resolve another way.

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 no parameter semantics to explain; the baseline of 4 applies. Nothing in the description misleads about inputs.

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 uses a specific verb ('Read') plus concrete resources ('radio settings, SSID status and associated clients'), so an agent knows exactly what it returns. It partially differentiates from siblings by excluding scan behavior, but never clarifies how it relates to the near-identical reading tools router_read and router_soap_read.

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?

The clause 'Does not start a radio scan' gives a genuine exclusion that tells the agent when this tool is insufficient. However, it stops short of naming the alternative to use for an actual scan or distinguishing this from router_read, leaving the selection between the read-family tools to inference.

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