Skip to main content
Glama
Sign In
mia

mia

by akadorkin
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

tailnet_devices

List every device in a Tailscale tailnet with online status, OS, client version, update availability, key expiry, tags, and inventory host mapping; filter by name, OS, tag, or offline days.

Instructions

Every device of the tailnet (Tailscale API with TAILSCALE_API_KEY, else this machine's tailscale status): online / last seen, OS and client version, update available, node key expiry, tags — and which inventory host and panel node it is.

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

Input Schema

NameRequiredDescriptionDefault
filterNosubstring of the name / hostname / OS / tag
offlineDaysNoonly devices offline for at least this many days

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations, the description carries the full burden, and it does add real behavioral context: the two possible data sources and the fallback logic, plus an enumeration of the fields returned (online/last seen, OS, version, update availability, key expiry, tags, host/panel mapping). It stops short of stating permissions or explicitly labeling the operation read-only.

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 dense sentence, front-loaded with the resource scope before the parenthetical about data source. It packs a lot of field information without wasted words, though the parenthetical interrupt is slightly awkward.

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 read-only listing tool with no output schema and two optional filters, the description covers the data source and the content of each returned record, which is enough for an agent to call it correctly. Missing only explicit safety/permission framing, which is minor here.

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?

Schema description coverage is 100% (both `filter` and `offlineDays` are documented in the schema), so the baseline is 3. The description adds no meaning for either parameter beyond what the schema already provides.

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 states a specific resource (every device of the tailnet) and enumerates the per-device attributes returned, so an agent can distinguish it from siblings like tailnet_join or tailnet_device_remove. It does not explicitly name those siblings, but the enumeration scope makes its role unambiguous.

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?

Usage is only implied: the agent infers it should call this to inventory devices. The parenthetical explains the data-source fallback (TAILSCALE_API_KEY vs local `tailscale status`), which is useful context, but there is no explicit when-to-use, when-not-to, or named alternative.

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

Deploy Server

Other Tools