Skip to main content
Glama

List Devices

list_devices
Read-onlyIdempotent

Retrieves connected and previously seen router devices, with case-insensitive filtering by hostname, IP, or MAC and options to limit or select returned fields.

Instructions

Devices the router knows about (connected and previously seen).

name_contains filters case-insensitively on any field (hostname, IP, MAC). Results are capped at limit. By default each device keeps a short field set (name, hostname, ip, ipv6, mac, mac_vendor, ui_type, ui_manufacturer, ui_model, activity, port, is_dhcp, time_last_active); pass fields to choose others (the router returns 41, for example user_agent, os, time_first_seen) or verbose for everything.

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

Input Schema

NameRequiredDescriptionDefault
limitNo
fieldsNo
verboseNo
name_containsNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.1

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare it read-only, closed-world, and idempotent, yet the description adds real behavioral context: results are capped at `limit`, the default response carries a named short field set, and `verbose` returns all 41 fields. That tells an agent the default output is truncated and how to widen it — information the annotations cannot convey.

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?

Purpose is front-loaded in one sentence, then parameter behavior follows in a compact paragraph with no filler. The long inline enumeration of default fields is information-dense but slightly heavy, which is the only structural cost.

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 no explanation, and the description covers default vs. verbose output shape and filtering adequately for a four-optional-parameter read tool. The missing piece is routing guidance relative to sibling listing tools, which is not essential to calling it correctly.

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?

Schema coverage is 0%, so the description must carry the burden, and it largely does: `name_contains` is documented as a case-insensitive match across hostname, IP, and MAC; `limit` caps results; `fields` and `verbose` are explained including the default field list and examples of extra fields. It omits the actual default value for `limit` (50) and the nullability of `fields`, keeping it from a 5.

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 opening line states the resource precisely — devices the router knows about, both connected and previously seen — which an agent can distinguish from the DNS, port-forward, and bandwidth siblings. The verb is implied (listing) rather than stated, and no sibling is named as an alternative, so it stops short of a 5.

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?

The description explains how to filter and shape results but never says when to choose this tool over router_status, get_host_traffic, or the other list_* siblings, nor any prerequisites or exclusions. Usage must be inferred entirely from the resource name.

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