Skip to main content
Glama
@yawlabs/tailscale-mcp

@yawlabs/tailscale-mcp

by YawLabs

Get user invite

tailscale_get_user_invite
Read-onlyIdempotent

Retrieve details for a specific Tailscale user invite using its invite ID, so you can inspect its status and metadata.

Instructions

Get details for a specific user 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_user_invite"
  }
}

Input Schema

NameRequiredDescriptionDefault
inviteIdYesThe user 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.6/5.0
Behavior2/5

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

The annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is fully covered elsewhere. The description adds nothing beyond that — no note on what an invite record contains, whether expired/accepted invites are still retrievable, or what happens for an unknown ID.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is a single short sentence with no wasted words, which is good structurally, but the brevity comes at the cost of information rather than being efficiently front-loaded. It reads as under-specification rather than disciplined conciseness.

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?

This is a simple read-only tool with one required parameter and no output schema, so not much is strictly needed. However, with no output schema the description should hint at what 'details' comprise, and it does not, leaving the agent to discover the response shape by calling it.

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 single inviteId parameter is documented in the schema as 'The user invite ID', so the schema carries the burden. The description only implies the ID-based lookup via the word 'specific' and adds no format or sourcing guidance beyond the schema.

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

Purpose3/5

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

The description names a verb ('Get details') and a resource ('user invite'), but it is nearly a restatement of the tool name and title. The only added nuance is 'specific', which hints at a single-invite lookup rather than a list, but it never states what details are returned or how this differs from siblings like tailscale_list_user_invites or tailscale_get_device_invite.

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 explicit guidance on when to use this tool versus tailscale_list_user_invites, tailscale_get_device_invite, or the create/delete/resend invite siblings. Usage is only inferable from the tool name and the required inviteId parameter.

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