Skip to main content
Glama
@yawlabs/tailscale-mcp

@yawlabs/tailscale-mcp

by YawLabs

Set device routes

tailscale_set_device_routes
DestructiveIdempotent

Replaces the enabled subnet routes for a Tailscale device by setting the full CIDR list, enabling you to update route access in one call.

Instructions

Set the enabled subnet routes for a device. Replaces all currently enabled routes -- pass the full list of routes you want enabled.

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>",
      "routes": "<routes>"
    },
    "name": "tailscale_set_device_routes"
  }
}

Input Schema

NameRequiredDescriptionDefault
routesYesFull list of CIDR routes to enable (e.g. ['10.0.0.0/24', '192.168.1.0/24']). Replaces existing enabled routes.
deviceIdYesThe device ID. 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.21.0
    • changedInput schema / properties / deviceId / description
      Previous value: -"The device ID"New value: +"The device ID. nodeId from tailscale_list_devices (e.g. nPM2KNuedB21DEVEL); numeric id ok; not the nodeKey."
  2. First observedv0.13.3

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true and idempotentHint=true; the description reinforces this by saying all currently enabled routes are replaced, which tells the agent what gets destroyed. Beyond that it adds little – no note on whether routes must be advertised/approved on the device, no permission requirements, and no confirmation that re-sending the same list is a no-op.

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 the replacement semantics front-loaded immediately after the purpose statement; nothing is redundant or padded.

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 two-parameter destructive setter with full schema coverage, the description covers purpose and the replace-not-merge contract, which is the main risk of misuse. Minor gaps remain around route validity/approval prerequisites and error behavior, but no output schema is needed for a simple mutation.

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 both parameters are documented, including the warn that deviceId must be the nodeId from tailscale_list_devices and not the nodeKey, plus a CIDR example for routes. The description only restates 'pass the full list', adding little beyond the schema, so baseline 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 ("Set the enabled subnet routes for a device"), which an agent can cleanly separate from the read-only sibling tailscale_get_device_routes and from tailscale_set_device_ip/tags. It stops short of naming those siblings explicitly, so it is clear but not maximally differentiated.

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?

Gives the crucial usage rule: the call replaces all currently enabled routes, so the caller must supply the complete desired list rather than a delta. It does not say when to prefer this over related tools or suggest calling get_device_routes first to read current state, so it falls short of full when/when-not guidance.

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