Skip to main content
Glama
YawLabs

@yawlabs/tailscale-mcp

by YawLabs
OverviewSchemaSourceRelated ServersScoreDiscussionsAdmin
TypeScript
Remote

tailscale_set_device_posture_attribute

Idempotent

Set or update custom posture attributes on devices to enforce compliance, JIT access, and custom security policies. Use 'custom:' keys with an optional expiry time.

Instructions

Set a custom posture attribute on a device. Creates or updates the attribute. Attribute keys must start with 'custom:'. Useful for compliance tracking, JIT access, and custom security policies.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
valueYesThe attribute value (string, number, or boolean)
expiryNoOptional expiry time in RFC3339 format (e.g. '2026-12-01T00:00:00Z'). Attribute is automatically removed after expiry.
deviceIdYesThe device ID
attributeKeyYesThe attribute key (must start with 'custom:', e.g. 'custom:lastAuditDate')

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.18.0
    • removedInput schema / properties / value / anyOf
      Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "number"
-  },
-  {
-    "type": "boolean"
-  }
-]
    • addedInput schema / properties / value / type
      Added value: +[
+  "string",
+  "number",
+  "boolean"
+]
  2. First observedv0.13.3

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already establish that this is a mutating, idempotent, non-destructive operation. The description adds behavioral context by explaining the create-or-update behavior, the required 'custom:' key prefix, and practical use cases. It does not discuss auth requirements or side effects, but the annotation coverage lowers the burden.

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?

Four short sentences with the main action front-loaded, followed by the key constraint and intended use cases. Every sentence adds useful information and there is no filler.

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

Completeness5/5

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

For this simple set operation, the combination of annotations, complete schema descriptions, and a concise tool description provides everything an agent needs: behavior, idempotency, key format, value types, optional expiry, and likely use cases. An output schema is not necessary for a setter.

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 each parameter documented including type constraints and expiry behavior. The tool description only restates the 'custom:' prefix already present in the attributeKey description, so it adds no new parameter-level meaning beyond the schema.

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?

The description clearly states the action ('Set'), the resource ('custom posture attribute on a device'), and the create-or-update semantics. This distinguishes it from sibling tools like getting, deleting, or batch-updating posture attributes.

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 description gives implied use cases ('compliance tracking, JIT access, and custom security policies') but never explicitly says when to choose this tool over tailscale_batch_update_posture_attributes or when not to use it. No exclusions or alternative routing are provided.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools