Skip to main content
Glama
Groupthink-dev

tailscale-blade-mcp

ts_approve_routes

Approve subnet routes on a Tailscale device. Additive by default to keep existing approvals; use replace=true to overwrite the entire route set.

Instructions

Approve subnet routes on a device. Requires TAILSCALE_WRITE_ENABLED=true.

Default (replace=false): additive — reads the device's currently enabled routes first and approves the union, so previously approved routes are preserved.

replace=true: raw Tailscale set-routes REPLACE semantics — the enabled set becomes exactly routes; any currently enabled route not listed is de-approved, which can sever subnet connectivity. Use only when you intend to remove approvals.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
device_idYesDevice nodeId (from ts_devices)
routesYesSubnet routes to approve (e.g. ['192.168.1.0/24'])
replaceNoReplace the device's entire enabled-route set with exactly `routes` instead of additively approving. WARNING: replace=true de-approves every currently-enabled route not listed — this can disconnect subnets.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

No annotations provided, but description fully discloses additive vs replace semantics, the destructive nature of replace=true, and the required env var. No contradictions.

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

Conciseness4/5

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

Well-structured: summary line, env requirement, then two modes. Slightly verbose but all content is relevant and earns its place.

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?

Complete for a mutation tool with two modes. Output schema exists to cover return format. Covers prerequisite, behavior, and warning. No gaps.

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 has 100% coverage with good descriptions. Description adds value by explaining default behavior of 'replace' parameter and warning about its impact.

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?

Clear verb 'Approve' and resource 'subnet routes on a device'. Distinguishes from sibling tool 'ts_device_routes' which is for listing. Also notes environment requirement.

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 contrasts default additive behavior with replace=true, warns of severity. Mentions prerequisite env var. Could be improved by stating when to use alternatives like ts_device_routes for viewing.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Groupthink-dev/tailscale-blade-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server