Skip to main content
Glama
@yawlabs/tailscale-mcp

@yawlabs/tailscale-mcp

by YawLabs

Get posture integration

tailscale_get_posture_integration
Read-onlyIdempotent

Retrieves details for a specific device posture integration by ID, so you can inspect its configuration and status in your Tailscale tailnet.

Instructions

Get details for a specific device posture integration.

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": {
      "integrationId": "<integrationId>"
    },
    "name": "tailscale_get_posture_integration"
  }
}

Input Schema

NameRequiredDescriptionDefault
integrationIdYesThe posture integration ID

Schema Changelog

Changes observed during successful MCP inspections.

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

TDQS

B3.1/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=true, so the safety and idempotency profile is covered. The description adds no further behavioral context such as what happens with an unknown or malformed integrationId, or what error surfaces on a miss.

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 short sentence, front-loaded with the verb and resource, with no filler or redundancy. Every word earns its place for a single-parameter read tool.

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?

For a simple one-parameter read this is close to adequate, but with no output schema the description does not say what 'details' actually comprises (providers, tenant IDs, posture attributes, timestamps). An agent knows how to call it but not what it will receive back.

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% with a single required string parameter ('The posture integration ID'), so the schema already carries the parameter meaning. The description contributes nothing beyond that, which matches the baseline of 3 when the schema does the heavy lifting.

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?

Description pairs a specific verb (Get) with a specific resource (device posture integration) and scopes it to one record via 'specific', which implicitly distinguishes it from tailscale_list_posture_integrations. It stops short of naming any sibling explicitly, so it is clear but not fully differentiated.

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 explicit guidance on when to use this versus tailscale_list_posture_integrations or tailscale_get_device_posture_attributes, and no mention of prerequisites. The only implied usage comes from the word 'specific', leaving the agent to infer the single-item vs list distinction.

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