Skip to main content
Glama
@yawlabs/tailscale-mcp

@yawlabs/tailscale-mcp

by YawLabs

List device invites

tailscale_list_device_invites
Read-onlyIdempotent

List all device invites for a specific Tailscale device using its device ID, so you can review pending share invitations for that device.

Instructions

List all device invites for a specific device.

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": {
      "deviceId": "<deviceId>"
    },
    "name": "tailscale_list_device_invites"
  }
}

Input Schema

NameRequiredDescriptionDefault
deviceIdYesThe device ID to list invites for. nodeId from tailscale_list_devices (e.g. nPM2KNuedB21DEVEL); numeric id ok; not the nodeKey.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.23.1
    • addedInput schema / properties / deviceId / minLength
      Added value: +1
  2. Changed1 schema field changedv0.21.0
    • changedInput schema / properties / deviceId / description
      Previous value: -"The device ID to list invites for"New value: +"The device ID to list invites for. nodeId from tailscale_list_devices (e.g. nPM2KNuedB21DEVEL); numeric id ok; not the nodeKey."
  3. First observedv0.13.3

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is fully covered; the description adds nothing on top. It says nothing about result shape, whether pending vs accepted invites are included, or pagination, which are the behaviors an agent would actually benefit from here.

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 short sentence with no filler and the object of the call front-loaded. It is efficient, though so terse that conciseness is partly achieved by omitting content.

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

Completeness3/5

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

For a one-parameter read-only listing tool with a fully documented schema and complete annotations, the essentials are present. Still missing is any hint about what the listing contains (pending/expired invites) or empty-result behavior, which is the remaining gap for a tool that returns a collection with no output schema.

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 coverage is 100% and the schema description is unusually rich (nodeId from tailscale_list_devices, numeric id acceptable, explicitly not nodeKey). The description only restates 'a specific device' and adds no meaning beyond the schema, so the baseline 3 applies.

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 gives a specific verb and resource (list device invites) scoped to a device, which is more precise than the bare title. It does not, however, distinguish itself from the near neighbours tailscale_list_user_invites or tailscale_get_device_invite, so an agent must infer the split from names alone.

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 statement of when to use this tool versus tailscale_get_device_invite (single invite) or the user-invite variants, and no prerequisites or exclusions. Usage is only implied by the phrase 'for a specific device'.

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