Skip to main content
Glama
@yawlabs/tailscale-mcp

@yawlabs/tailscale-mcp

by YawLabs

Resend user invite

tailscale_resend_user_invite

Resend a pending user invite email using its invite ID. Use it when a Tailscale tailnet invite was not received or expired so the recipient gets a new invite email.

Instructions

Resend a user 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_user_invite"
  }
}

Input Schema

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

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

The annotations already mark this as a non-read-only, non-idempotent, open-world operation that is not destructive. Beyond that, the description adds nothing: it does not say whether the resend invalidates the previous invitation link, what the response looks like, or what happens if the invitee has already accepted the invite or the invite has expired.

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?

One short sentence with no filler and no redundant clauses. Its leanness is appropriate, though it is lean because it omits information rather than because it is tightly packed.

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?

Given the tool's low complexity (one fully documented parameter, annotations present, and no output schema), the description is barely adequate. It is incomplete on the behavioral side: the agent knows what to call, but not whether the call is safe to retry or what it changes for the invitee.

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 inviteId already documents 'The user invite ID to resend', so the description does not need to compensate. The description adds no meaning about the ID's format or source, so the baseline score of 3 applies.

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 phrase 'Resend a user invite email' names a specific verb (resend) and resource (user invite), and the added word 'email' tells the agent that mail delivery is involved. But it is nearly a verbatim restatement of the tool name and title, so it does little more than confirm what the identifier already says.

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?

The description gives no guidance on when to use this tool instead of its close siblings, such as tailscale_create_user_invite, tailscale_get_user_invite, tailscale_delete_user_invite, or tailscale_resend_device_invite. It does not state prerequisites either: whether the invite must still be valid, whether it may be expired, or whether a rate limit applies.

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