Skip to main content
Glama
@yawlabs/tailscale-mcp

@yawlabs/tailscale-mcp

by YawLabs

Get device invite

tailscale_get_device_invite
Read-onlyIdempotent

Retrieve details for a specific Tailscale device invite by invite ID to inspect its status and metadata.

Instructions

Get details for a specific device invite.

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": {
      "inviteId": "<inviteId>"
    },
    "name": "tailscale_get_device_invite"
  }
}

Input Schema

NameRequiredDescriptionDefault
inviteIdYesThe device invite ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.23.1
    • addedInput schema / properties / inviteId / minLength
      Added value: +1
  2. 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=true, idempotentHint=true, openWorldHint=true and destructiveHint=false, so the safety profile is fully covered by structured data. The description adds nothing beyond that — no note on what a returned invite contains, whether expired or accepted invites are still retrievable, or what happens with an invalid ID.

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 front-loaded sentence with zero filler, so nothing is wasted. However, the terseness borders on under-specification given the number of closely related invite tools in the sibling list.

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 tool with full annotation coverage, the definition is minimally sufficient to invoke correctly. It leaves gaps an agent would want: how to obtain the inviteId, and how this differs from tailscale_list_device_invites and tailscale_get_user_invite.

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 required parameter with 100% schema description coverage ("The device invite ID"), so the schema carries the semantics. The description's phrase "a specific device invite" implicitly confirms the ID-based lookup but adds no format, source, or validation meaning beyond the schema.

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 verb and resource ("Get details for a specific device invite"), which clearly reads as a single-item fetch. It does not explicitly distinguish itself from siblings like tailscale_list_device_invites or tailscale_get_user_invite, though "specific" implies single-record retrieval.

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 guidance on when to use this tool versus tailscale_list_device_invites (to find an ID first) or tailscale_get_user_invite (for the user-invite counterpart). No prerequisites, no exclusions, no error conditions such as an unknown or expired inviteId are mentioned.

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