tslink

Overview Schema Source Related Servers Discussions Admin

Revoke an invitation

invite_revoke

DestructiveIdempotent

Cancel an outstanding Tailscale invitation to block acceptance; confirm with the user first because it can't be undone, then issue a new one if needed.

Instructions

Cancels a real outstanding invitation on the user's tailnet, so confirm with the user before calling this. A revoked invitation can no longer be accepted and cannot be un-revoked; issue a new one instead. Use invite_list to find the id.

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": {
      "kind": "<kind>",
      "invite_id": "<invite_id>"
    },
    "name": "invite_revoke"
  }
}

Input Schema

Name	Required	Description	Default
`kind`	Yes	Invite namespace the id belongs to.
`invite_id`	Yes	Invite id from invite_list.

Output Schema

Name	Required	Description	Default
`id`	Yes
`kind`	Yes
`revoked`	Yes
`service`	No
`remote_side_effect_plan`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 19, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Goes beyond the annotations by disclosing irreversibility ('cannot be un-revoked') and a user-confirmation requirement, which the destructiveHint/idempotentHint flags alone do not convey. This is exactly the extra context that raises confidence for a destructive, open-world mutation.

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

Conciseness5/5

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

Three sentences, front-loaded with the confirmation caution, then the irreversibility consequence, then the id-lookup pointer. Every sentence carries distinct, actionable information with no filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With an output schema present and annotations covering the safety profile, the description fills the remaining gaps: irreversibility, confirmation, and how to obtain the required id. Nothing needed to invoke it correctly is missing.

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 enum values for 'kind' are documented in the schema, so the baseline is 3. The description adds a minor provenance pointer ('from invite_list') but no syntax or format detail beyond what the schema already provides.

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

Purpose5/5

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

States a specific verb and resource: 'Cancels a real outstanding invitation on the user's tailnet.' This clearly identifies the action and scope, distinguishing it from the many other revoke/list siblings (guest_revoke, people_revoke, invite_list) without opening either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly instructs to 'confirm with the user before calling this' and directs the agent to 'Use invite_list to find the id,' covering both the caution and the precondition. It also states the alternative for reversing course ('issue a new one instead'), so when/when-not is fully specified.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.