tailscale-blade-mcp

ts_device

Retrieve complete details for a single Tailscale device: addresses, OS, client version, key status, tags, and user identified by device ID.

Instructions

Full detail for a single device: addresses, OS, client version, key status, tags, user.

Single-record fetch — server-side filter is device_id-shaped, not tag-shaped. The _meta envelope is emitted for audit-surface uniformity; scope= is intentionally NOT accepted here because a scope filter on a single-device-detail call is semantically incoherent.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "device_id": "<device_id>"
    },
    "name": "ts_device"
  }
}

Input Schema

Name	Required	Description	Default
`device_id`	Yes	Device nodeId (from ts_devices)

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.9.0Jun 25, 2026

TDQS

A4.6/5.0

Behavior4/5

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

With no annotations, the description carries full burden. It discloses the return of a _meta envelope for audit uniformity and clarifies that scope filtering is not supported. It doesn't mention auth or error conditions, but for a simple fetch this is adequate.

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?

The description is two efficient sentences plus a clarifying note. It starts with the core purpose ('Full detail for a single device') and then provides behavioral constraints. No wasted words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's simplicity, high schema coverage, and existence of an output schema, the description is complete. It explains the return details, filter behavior, and scope exclusion, leaving no major gaps for a single-record fetch tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and the description adds value by clarifying that the device_id parameter is 'device nodeId (from ts_devices)' and that it's 'server-side filter ... not tag-shaped'. It also warns about scope not being accepted, enhancing schema meaning.

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

Purpose5/5

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

The description clearly states it returns 'Full detail for a single device' listing specific fields (addresses, OS, client version, etc.). It distinguishes from sibling tools by emphasizing it's a single-record fetch using device_id, contrasting with tag-based or list operations.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explicitly says 'Single-record fetch' and notes that 'scope= is intentionally NOT accepted' due to semantic incoherence, providing clear when-not guidelines. However, it does not explicitly name alternative sibling tools like ts_devices for listing.

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