Skip to main content
Glama
@yawlabs/tailscale-mcp

@yawlabs/tailscale-mcp

by YawLabs

Create device invite

tailscale_create_device_invite

Create a device share invitation to grant an external user access to a specific device in your tailnet, with optional email, multi-use, and exit-node settings.

Instructions

Create a device share invitation that allows an external user to access a specific device in your tailnet.

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

Input Schema

NameRequiredDescriptionDefault
emailNoEmail address to send the invite to
deviceIdYesThe device ID to create an invite for. nodeId from tailscale_list_devices (e.g. nPM2KNuedB21DEVEL); numeric id ok; not the nodeKey.
multiUseNoWhether the invite can be used more than once (default: false)
allowExitNodeNoWhether the invited device can be used as an exit node (default: false)

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 create an invite for"New value: +"The device ID to create an invite for. nodeId from tailscale_list_devices (e.g. nPM2KNuedB21DEVEL); numeric id ok; not the nodeKey."
  3. Changed1 schema field changedv0.19.1
    • changedInput schema / properties / email / pattern
      Previous value: -"^(?!\\.)(?!.*\\.\\.)([A-Za-z0-9_'+\\-\\.]*)[A-Za-z0-9_+-]@([A-Za-z0-9][A-Za-z0-9\\-]*\\.)+[A-Za-z]{2,}$"New value: +"^(?:[A-Za-z0-9_'+\\-]+\\.)*[A-Za-z0-9_'+\\-]*[A-Za-z0-9_+-]@(?:[A-Za-z0-9][A-Za-z0-9\\-]*\\.)+[A-Za-z]{2,}$"
  4. First observedv0.13.3

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, idempotentHint=false, openWorldHint=true (external user), and destructiveHint=false, so the safety profile is largely covered. The description contributes real context by naming the external-recipient, single-device sharing model, but says nothing about invite expiry, whether an email is actually dispatched, or that repeated calls create distinct invites (non-idempotent in a user-visible way).

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 no filler or repetition, and the key scope qualifier is placed early. It is efficient, though it is terse enough that some guidance is simply absent rather than compactly expressed.

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 non-destructive create operation with full annotation coverage, a 100%-documented schema, and no output schema, the description is adequate. It omits what the agent gets back (invite id/link), whether an email is sent, and any expiry or permission requirement — gaps that matter for an invite-creation flow but are partly mitigated by the rich schema and annotations.

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 description coverage is 100%, and the schema itself is unusually helpful (e.g., deviceId explains nodeId vs numeric id vs nodeKey, defaults for multiUse and allowExitNode). The description adds no parameter-level meaning beyond what that schema already provides, 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?

States a specific verb and resource ("Create a device share invitation") plus the scope ("access a specific device in your tailnet"), which is meaningfully more precise than the title alone. It does not explicitly distinguish this from sibling invite tools such as tailscale_create_user_invite or tailscale_accept_device_invite, so the sibling differentiation part is left implicit.

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?

No guidance on when to choose this over the user-invite or key-creation siblings, and no prerequisites stated (owner/admin rights, whether the device must be authorized, whether the recipient needs to accept). The reader must infer the usage context entirely from the one-sentence purpose.

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