Skip to main content
Glama
@yawlabs/tailscale-mcp

@yawlabs/tailscale-mcp

by YawLabs

Approve user

tailscale_approve_user
Idempotent

Approve a pending Tailscale user by user ID, granting them access to the tailnet.

Instructions

Approve a pending user, granting them access to the tailnet.

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": {
      "userId": "<userId>"
    },
    "name": "tailscale_approve_user"
  }
}

Input Schema

NameRequiredDescriptionDefault
userIdYesThe user ID to approve

Schema Changelog

Changes observed during successful MCP inspections.

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

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnly=false, idempotent=true, destructive=false, and openWorld=true, so the safety profile is covered. The description adds genuine context by stating the effect is granting tailnet access, but it omits irreversibility (does approval need to be undone via suspend?), error behavior for non-pending users, and permission requirements — gaps that matter for a write operation.

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?

One front-loaded sentence with the action first and the consequence second; no filler, no repetition of 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 one-parameter tool with full schema coverage, an output schema absent, and annotations covering mutability and idempotency, almost everything an agent needs is present. The only residual gap is guidance on what happens when the target user is not in a pending state.

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?

There is a single parameter with 100% schema description coverage ("The user ID to approve"), so the schema carries the semantics. The description adds nothing about the ID format or where it comes from, which is acceptable at this coverage level but not value-adding.

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?

The description names a specific verb and resource ("approve a pending user") plus the effect ("granting them access to the tailnet"), which clearly separates it from siblings like tailscale_suspend_user, tailscale_restore_user, and tailscale_delete_user. It stops short of explicitly naming those alternatives, so it isn't a 5.

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?

The phrase "pending user" implies the precondition for use, but the description never states what to do instead for users in other states (suspend/restore/update role) or what happens if the user is not pending. Usage is inferable but not spelled out.

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