Skip to main content
Glama
@yawlabs/tailscale-mcp

@yawlabs/tailscale-mcp

by YawLabs

Get key

tailscale_get_key
Read-onlyIdempotent

Retrieve details for a Tailscale auth key, API token, OAuth client, or federated identity by key ID, including revoked or expired keys marked invalid.

Instructions

Get details for a specific key (auth key, API access token, OAuth client, or federated identity). A revoked or expired key is still returned, with invalid: true.

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": {
      "keyId": "<keyId>"
    },
    "name": "tailscale_get_key"
  }
}

Input Schema

NameRequiredDescriptionDefault
keyIdYesThe key ID (auth key, API access token, OAuth client, or federated identity)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.23.1
    • addedInput schema / properties / keyId / minLength
      Added value: +1
  2. Changed1 schema field changedv0.21.0
    • changedInput schema / properties / keyId / description
      Previous value: -"The key ID (auth key, OAuth client, or federated identity)"New value: +"The key ID (auth key, API access token, OAuth client, or federated identity)"
  3. First observedv0.13.3

TDQS

A4/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), so the description's added value is the disclosure that revoked or expired keys are still returned with `invalid: true` rather than erroring — genuinely useful, non-obvious behavior. Minor gaps remain (no note on what happens for an unknown keyId), but the core edge case is covered.

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, front-loaded with the core action and scope, then the one non-obvious behavioral detail. No boilerplate or redundancy.

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 single-parameter read tool with no output schema, the definition covers scope and the key edge case (invalid: true). It could note how to obtain a keyId or whether other key fields are returned, but nothing essential to correct invocation is missing.

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 coverage is 100% and the single keyId parameter is fully documented there; the description's parenthetical about key types restates what the schema already says. It adds no format, prefix, or lookup guidance 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.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (get) and resource (a specific key) and enumerates the four key kinds it covers — auth key, API access token, OAuth client, federated identity — which distinguishes it from siblings like tailscale_get_oauth_app or tailscale_list_keys. An agent can identify the right tool without opening the schema.

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 implied by 'a specific key' (i.e., requires a known keyId), but it never names the alternative for discovery (tailscale_list_keys) or exclusions such as OAuth-app-level details handled by tailscale_get_oauth_app. No explicit when-to-use/when-not-to-use 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