ableton-mcp

Overview Schema Source Related Servers Discussions Admin

claim_nks_generation_job

Destructive

Atomically lease one pending NKS generation job for a worker and return its catalog preset without loading the plugin or saving a file.

Instructions

Atomically lease one pending NKS generation job for a worker. Returns its catalog preset without loading the plugin or saving a file.

Input Schema

Name	Required	Description	Default
`workerId`	Yes	Non-empty worker identity.
`productSlug`	Yes	Exact product slug.

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv0.3.1Oct 23, 2026

removedOutput schema / additionalProperties
```
Removed value: -true
```

addedOutput schema / anyOf

Added value: +[
+  {
+    "properties": {
+      "job": {
+        "anyOf": [
+          {
+            "type": "object"
+          },
+          {
+            "type": "null"
+          }
+        ]
+      },
+      "preset": {
+        "anyOf": [
+          {
+            "type": "object"
+          },
+          {
+            "type": "null"
+          }
+        ]
+      }
+    },
+    "required": [
+      "job",
+      "preset"
+    ],
+    "type": "object"
+  },
+  {
+    "properties": {
+      "error": {
+        "properties": {
+          "message": {
+            "type": "string"
+          },
+          "outcome": {
+            "enum": [
+              "unknown",
+              "not_executed"
+            ]
+          }
+        },
+        "required": [
+          "message",
+          "outcome"
+        ],
+        "type": "object"
+      }
+    },
+    "required": [
+      "error"
+    ],
+    "type": "object"
+  }
+]

Changed1 schema field changedv0.3.0Oct 19, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "type": "object"
+}

Addedv0.2.0Sep 30, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already declare destructiveHint=true, non-idempotent, and closed-world. The description adds genuinely useful behavioral context beyond them: the lease is atomic (no double-claim race) and does not load the plugin or save a file, which bounds the side effects of an otherwise 'destructive' claim. It doesn't cover lease expiry/timeout semantics, which would be nice for a non-idempotent mutator.

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 tightly packed sentences with no waste. The action and the atomicity constraint come first, then the return/side-effect clarification.

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?

With an output schema present, return values needn't be explained, and the description still clarifies that the preset is returned without plugin load or file writes. The main missing element is lease lifetime/timeout behavior for a non-idempotent claim, which matters operationally.

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%, so both required parameters are documented in the schema itself. The description only echoes 'for a worker' and never explains the productSlug scoping role; baseline 3 applies since the schema carries the load.

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 — atomically lease one pending NKS generation job for a worker — which is a distinct action from the read sibling get_nks_generation_job and the complete/fail siblings. It does not name those siblings explicitly, so the differentiation is implicit rather than spelled out.

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 'for a worker' and 'one pending job' implies the queue-consumer context, but there is no explicit guidance on when to claim versus reading status with get_nks_generation_job or when to complete/fail a claimed job. The agent must infer the workflow.

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

Deploy Server