Skip to main content
Glama
@yawlabs/tailscale-mcp

@yawlabs/tailscale-mcp

by YawLabs

Restore user

tailscale_restore_user
Idempotent

Restore a suspended Tailscale user to re-grant their access to the tailnet.

Instructions

Restore a previously suspended user, re-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_restore_user"
  }
}

Input Schema

NameRequiredDescriptionDefault
userIdYesThe user ID to restore

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.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=true, and openWorldHint=true, so safety and repeatability are covered. The description adds the meaningful consequence that tailnet access is re-granted, but omits permission requirements, error behavior for non-suspended users, and whether other user attributes are touched.

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?

A single front-loaded sentence with zero filler that states the precondition and the effect together. It is efficient, though it packs both facts into one clause rather than separating the operation from its outcome.

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 mutation tool with full annotation coverage and no output schema, the description conveys what the tool does and its precondition. Only the failure mode for a non-suspended user and any return value expectations remain unstated, which is minor at this complexity.

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 restore"), so the schema already carries the load. The description adds no format or sourcing guidance for userId, so the 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?

The description names a specific verb and resource ("Restore a ... user") and scopes it to a "previously suspended" user, which implicitly separates it from tailscale_suspend_user, tailscale_approve_user, and tailscale_delete_user. It stops short of naming those siblings explicitly, so an agent must still infer the boundary from the wording.

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?

Usage is only implied: the phrase "previously suspended user" tells the agent the tool applies to suspended accounts, but there is no statement of when to prefer this over approve_user or delete_user, and no mention of what happens if the user is not currently suspended. Adequate minimum, with clear gaps.

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