tailscale-blade-mcp

ts_delete_key

Revoke an auth key permanently. Requires explicit confirmation to prevent unintended key deletion.

Instructions

Revoke an auth key. Requires TAILSCALE_WRITE_ENABLED=true and confirm=true.

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": {
      "key_id": "<key_id>"
    },
    "name": "ts_delete_key"
  }
}

Input Schema

Name	Required	Description	Default
`key_id`	Yes	Auth key ID to revoke (from ts_keys)
`confirm`	No	Must be true to confirm — revokes the key permanently

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.9.0Jun 25, 2026

TDQS

A4.7/5.0

Behavior5/5

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

No annotations provided, but the description discloses that this is a destructive write operation requiring confirmation and a write-enabled flag. The confirm parameter's schema description adds clarity about permanent revocation.

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?

Single sentence with no wasted words. The key action and all requirements are front-loaded and clearly stated.

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?

For a simple tool with an output schema, the description covers purpose, prerequisites, and parameter semantics adequately. No missing elements needed for correct usage.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, and the main description adds context by requiring confirm=true, which is not enforced by the schema (only a default of false). This extra guidance helps the agent understand the parameter's role.

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?

The description clearly states the action 'Revoke an auth key' with a specific verb and resource. It distinguishes from sibling tools like ts_create_key and ts_keys which perform opposite or related actions.

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

Usage Guidelines4/5

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

Explicitly states prerequisites (TAILSCALE_WRITE_ENABLED=true and confirm=true) but does not specify when not to use or list alternatives. Context is clear enough for a simple destructive operation.

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