Skip to main content
Glama
@yawlabs/tailscale-mcp

@yawlabs/tailscale-mcp

by YawLabs

Get user

tailscale_get_user
Read-onlyIdempotent

Retrieves details for a specific Tailscale user by user ID so you can inspect account information in your tailnet.

Instructions

Get details for a specific user.

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_get_user"
  }
}

Input Schema

NameRequiredDescriptionDefault
userIdYesThe user ID

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

C2.9/5.0
Behavior2/5

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

The annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered elsewhere. The description adds nothing beyond that: it does not mention error behavior for nonexistent users, permission requirements, or what the returned record contains, so it earns little credit beyond annotations.

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 short sentence with no filler, and the resource being fetched is front-loaded in the title and body. It is efficient, though the extreme brevity is achieved partly by omitting useful detail rather than by tight editing.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool is simple (one required string parameter, rich annotations, no nested objects) and there is no output schema, so some description of the returned user record would be helpful. Given the low complexity, the definition is adequate to call correctly but does not tell the agent what 'details' means or how to handle an unknown userId.

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 there is only one required parameter (userId) with its own description in the schema. The tool description adds no format hints (e.g., numeric ID vs. email/login) beyond the schema, 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 (get) and resource (user) and scopes it to a single record via 'a specific user', which is distinguishable from the sibling tailscale_list_users. It stops short of explicitly contrasting itself with that sibling, so it is clear but not maximally differentiating.

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

Usage Guidelines2/5

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

There is no guidance on when to use this tool versus tailscale_list_users or the many user-management siblings (approve, suspend, restore, update role, delete). The single-ID lookup intent is implied only by the word 'specific', leaving the agent to infer prerequisites such as whether the ID is a numeric ID or a login name.

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