Skip to main content
Glama

list_clients

Read-onlyIdempotent

List connected and optionally inactive devices on a TP-Link router, including hostname, IP, MAC, connection type, Wi-Fi band/SSID, signal strength, and link rate.

Instructions

Devices on the network: hostname, IP, MAC, wired or Wi-Fi band and SSID, signal (dBm, closer to 0 is better; below -75 is weak) and link rate where the router reports them.

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

Input Schema

NameRequiredDescriptionDefault
include_inactiveNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3.2/5.0
Behavior3/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 still contributes genuine context: signal semantics (closer to 0 is better, below -75 is weak) and the caveat 'where the router reports them', which warns that fields may be absent. It does not say whether results reflect a live poll or a cached snapshot.

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?

One sentence, front-loaded with the resource and then the returned fields, with zero padding. The parenthetical signal interpretation earns its place; nothing is redundant.

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?

An output schema exists, so return values need not be spelled out, and the annotations cover the safety profile. The only real gap is the unexplained include_inactive flag and the absence of any note on result size or freshness.

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?

There is a single optional parameter, include_inactive, with 0% schema description coverage, and the description never mentions it. The phrase 'devices on the network' weakly implies active clients only, leaving the meaning of the flag to be guessed from its name.

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 (devices on the network) and enumerates exactly what each record carries — hostname, IP, MAC, wired/Wi-Fi band and SSID, signal, link rate. That is a precise picture of the tool's purpose, but it is phrased as a noun list rather than an action and never distinguishes it from siblings such as client_history or find_client.

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 statement, no exclusions, and no named alternative. An agent must infer from the name and field list that this is a current snapshot rather than the historical view offered by client_history.

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