Skip to main content
Glama
YawLabs

@yawlabs/tailscale-mcp

by YawLabs
OverviewSchemaSourceRelated ServersScoreDiscussionsAdmin
TypeScript
Remote

tailscale_batch_update_posture_attributes

Idempotent

Batch update custom posture attributes on multiple Tailscale devices in one operation. Set values and expiry under custom: keys, or pass null to delete an attribute.

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.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nodesYesMap 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.
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.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"
+  }
+]
  2. First observedv0.13.3

TDQS

A3.8/5.0
Behavior1/5

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

The description explicitly says 'pass null as the attribute config to delete', yet the annotations mark destructiveHint as false. This is a direct contradiction: the tool can delete attribute configuration, so the safety signal is misleading. Per the rubric, a contradiction forces a score of 1 even though the description adds useful JSON Merge Patch semantics.

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 tight sentences front-load the purpose and then give the essential behavioral constraints. No filler or unnecessary repetition of schema details.

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 mutation with a nested map parameter, the description plus fully documented schema give an agent enough to construct a valid call. The main remaining gap is the conflicting destructiveHint signal, and there is no output schema to describe the return value.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the schema already documents both parameters and the null-delete pattern. The description adds value beyond the schema by stating the 'custom:' key requirement and naming JSON Merge Patch semantics, which clarifies the behavior of omitted keys.

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 names the exact operation ('Batch update custom posture attributes'), the scope ('across multiple devices'), and the key namespace ('custom:'). This clearly distinguishes it from the sibling single-device set/delete posture attribute tools even without naming them.

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

Usage Guidelines4/5

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

'Batch update ... across multiple devices' clearly signals the multi-device use case and implies that single-device siblings should be used for one-off changes, but it does not explicitly state when-not-to-use or name alternatives.

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