Skip to main content
Glama
@yawlabs/tailscale-mcp

@yawlabs/tailscale-mcp

by YawLabs

Delete service

tailscale_delete_service
DestructiveIdempotent

Delete a Tailscale Service permanently, releasing its MagicDNS name and virtual IP. Use when you need to remove an existing service and cannot restore it.

Instructions

Delete a Tailscale Service. This is irreversible -- the service's MagicDNS name and virtual IP will be released.

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": {
      "serviceName": "<serviceName>"
    },
    "name": "tailscale_delete_service"
  }
}

Input Schema

NameRequiredDescriptionDefault
serviceNameYesThe service name to delete

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.23.1
    • addedInput schema / properties / serviceName / minLength
      Added value: +1
  2. First observedv0.13.3

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and openWorldHint=true, so the safety profile is covered, but the description adds the concrete consequence: the MagicDNS name and virtual IP are released. The 'irreversible' framing adds useful decision context beyond the hints, though there is mild tension with idempotentHint=true (the effect is permanent, but repeated calls are harmless) that could be spelled out.

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 redundancy; the operation and its consequence are front-loaded, making the risk visible before the agent commits.

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 one-parameter destructive tool with full annotation coverage, the description supplies the key missing piece (what is destroyed). It does not cover behavior when the service name does not exist, a minor omission rather than a blocking gap.

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?

With a single parameter at 100% schema description coverage, the schema already documents serviceName. The description adds no format details or naming-convention guidance beyond it, 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 ('Delete a Tailscale Service'), which unambiguously identifies the operation among siblings such as tailscale_get_service, tailscale_list_services and tailscale_update_service. It stops short of explicitly differentiating itself from those siblings, so it is clear but not maximally distinguishing.

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

Usage Guidelines3/5

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

There is no explicit 'use this when' guidance or mention of prerequisites such as confirming the service should be removed rather than updated or detached via tailscale_update_service. Usage is implied by the destructive verb, which is the minimum viable level.

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