Skip to main content
Glama
@yawlabs/tailscale-mcp

@yawlabs/tailscale-mcp

by YawLabs

Batch update posture attributes

tailscale_batch_update_posture_attributes
Idempotent

Batch update custom posture attributes across multiple devices using JSON Merge Patch semantics; set values or pass null to delete attributes.

Instructions

Batch update custom posture attributes across multiple devices. Each attribute key must start with 'custom:'. Uses JSON Merge Patch semantics -- pass null as the attribute config to delete.

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": {
      "nodes": "<nodes>"
    },
    "name": "tailscale_batch_update_posture_attributes"
  }
}

Input Schema

NameRequiredDescriptionDefault
nodesYesMap of device ID to attribute config map (e.g. { "nPM2KNuedB21DEVEL": { "custom:compliant": { "value": "true" } }, "nPpz3VEKzX11DEVEL": { "custom:compliant": { "value": false, "expiry": "2026-12-01T00:00:00Z" } } }). Keys are device IDs, nodeIds preferred. Pass null as the config to delete an attribute.
commentNoOptional comment added to the audit log explaining why attributes are being set (max 200 chars)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.21.0
    • changedInput schema / properties / nodes / description
      Previous value: -"Map of device ID to attribute config map (e.g. { \"12345\": { \"custom:compliant\": { \"value\": \"true\" } }, \"67890\": { \"custom:compliant\": { \"value\": false, \"expiry\": \"2026-12-01T00:00:00Z\" } } }). Pass null as the config to delete an attribute."New value: +"Map of device ID to attribute config map (e.g. { \"nPM2KNuedB21DEVEL\": { \"custom:compliant\": { \"value\": \"true\" } }, \"nPpz3VEKzX11DEVEL\": { \"custom:compliant\": { \"value\": false, \"expiry\": \"2026-12-01T00:00:00Z\" } } }). Keys are device IDs, nodeIds preferred. Pass null as the config to delete an attribute."
  2. Changed1 schema field changedv0.18.0
    • changedInput schema / properties / nodes / additionalProperties / additionalProperties / anyOf
      Previous value: -[
      -  {
      -    "properties": {
      -      "expiry": {
      -        "type": "string"
      -      },
      -      "value": {
      -        "anyOf": [
      -          {
      -            "type": "string"
      -          },
      -          {
      -            "type": "number"
      -          },
      -          {
      -            "type": "boolean"
      -          }
      -        ]
      -      }
      -    },
      -    "required": [
      -      "value"
      -    ],
      -    "type": "object"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "properties": {
      +      "expiry": {
      +        "type": "string"
      +      },
      +      "value": {
      +        "type": [
      +          "string",
      +          "number",
      +          "boolean"
      +        ]
      +      }
      +    },
      +    "required": [
      +      "value"
      +    ],
      +    "type": "object"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
  3. First observedv0.13.3

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare write, idempotent and non-destructive behavior; the description adds genuinely new behavioral facts: the 'custom:' key prefix requirement, JSON Merge Patch semantics, and that null config deletes an attribute. It does not mention the audit-log comment or any permission requirements, but the merge-patch disclosure is the key operational detail an agent would otherwise get wrong.

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?

Three short sentences, front-loaded with purpose, followed by the two operational constraints. No filler 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 nested-object write tool with a fully documented schema and no output schema, the description covers the essential gotchas: prefix rule, merge semantics and deletion. It could optionally note that existing attributes not mentioned are left untouched (a natural consequence of merge patch that agents may not infer).

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 schema already documents the null-to-delete behavior and the node map shape, so the description largely repeats structured data. The one added semantic is the 'custom:' prefix constraint on attribute keys, which the schema does not state.

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?

States a specific verb and resource ('Batch update custom posture attributes across multiple devices'), and the word 'batch' implicitly separates it from the single-device siblings like tailscale_set_device_posture_attribute. It does not name those siblings explicitly, so the differentiation is inferable rather than stated.

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 phrase 'across multiple devices' implies when this is preferable to a single-device setter, but there is no explicit when-to-use/when-not guidance and no pointer to tailscale_set_device_posture_attribute or tailscale_delete_device_posture_attribute as alternatives. Usage context is implied only.

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