Skip to main content
Glama
@yawlabs/tailscale-mcp

@yawlabs/tailscale-mcp

by YawLabs

Resend device invite

tailscale_resend_device_invite

Resend a Tailscale device invite email by invite ID to deliver a new invitation when the original was missed or expired.

Instructions

Resend a device invite email.

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_resend_device_invite"
  }
}

Input Schema

NameRequiredDescriptionDefault
inviteIdYesThe device invite ID to resend

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=false, idempotentHint=false, destructiveHint=false and openWorldHint=true, so the safety profile is covered structurally. The description adds nothing beyond them: it does not say that an email is dispatched to the invitee, whether the previous invite or its expiry is regenerated, or whether repeated calls are accepted — all relevant given idempotentHint=false.

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, which is appropriately sized for a one-parameter action tool. It is not front-loaded with any actionable context, but there is no wasted wording.

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?

The tool is simple (one required parameter, no output schema, no nested objects), so heavy documentation is not required. However, nothing is said about the observable outcome of a resend (email delivery, invite expiry reset, failure modes for non-pending invites), leaving the operational picture incomplete for a non-idempotent mutation.

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% with a single well-described required parameter ('The device invite ID to resend'), so the schema carries the semantics. The description adds no format hints, ID sourcing guidance (e.g., from tailscale_list_device_invites), or constraints, so the baseline of 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 states a specific verb and resource ('Resend a device invite email'), so an agent can identify the operation immediately. It does not distinguish itself from close siblings such as tailscale_resend_user_invite or tailscale_resend_contact_verification, which share the same resend semantics.

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 alternatives like tailscale_create_device_invite, tailscale_get_device_invite, or the user-invite resend variant. No preconditions (e.g., invite must be pending/not expired) or exclusions are stated.

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