Skip to main content
Glama
@yawlabs/tailscale-mcp

@yawlabs/tailscale-mcp

by YawLabs

Delete device

tailscale_delete_device
DestructiveIdempotent

Permanently remove a device from the tailnet by device ID. This action is irreversible; the device must re-authenticate to rejoin.

Instructions

Permanently remove a device from the tailnet. This is irreversible -- the device must re-authenticate to rejoin.

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

Input Schema

NameRequiredDescriptionDefault
deviceIdYesThe device ID to delete. nodeId from tailscale_list_devices (e.g. nPM2KNuedB21DEVEL); numeric id ok; not the nodeKey.

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 delete"New value: +"The device ID to delete. nodeId from tailscale_list_devices (e.g. nPM2KNuedB21DEVEL); numeric id ok; not the nodeKey."
  3. First observedv0.13.3

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, so the description's job is to add context — and it does, by spelling out irreversibility and the re-authentication cost to rejoin the tailnet. That is exactly the consequence an agent needs before committing a destructive call. It stops short of noting permission requirements or whether the device must be offline.

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?

Two short sentences with zero waste: the action and scope come first, the irreversible consequence second. Every clause earns its place and nothing is repeated from the title or annotations.

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

Completeness4/5

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

For a single-parameter destructive tool with no output schema, the definition covers what an agent needs: what it does and that it cannot be undone. Annotations carry the safety profile and the schema carries the identifier format. Only the authorization prerequisite is left unstated.

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 the deviceId property description is unusually rich, specifying nodeId from tailscale_list_devices, accepting a numeric id, and warning against nodeKey. The description adds no parameter meaning beyond that, which is the expected baseline when the schema already carries the semantics.

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?

"Permanently remove a device from the tailnet" states a specific verb (remove) and resource (device), and the word "permanently" implicitly separates it from siblings like tailscale_deauthorize_device or tailscale_expire_device. It never names those alternatives explicitly, so an agent still has to infer the distinction between removing, deauthorizing, and expiring a device.

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 explicit when-to-use or when-not-to-use guidance, and no sibling is named as an alternative. The phrase "the device must re-authenticate to rejoin" hints at consequences but does not tell an agent when deletion is the right choice over deauthorize, expire, or set_devices_authorized.

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