Skip to main content
Glama
cavi-ai

ableton-mcp

by cavi-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

heartbeat_nks_generation_job

Destructive

Extend an unexpired NKS generation lease for a preset and worker to prevent the job from expiring.

Instructions

Extend an unexpired NKS generation lease owned by this worker.

Input Schema

NameRequiredDescriptionDefault
presetIdYesNKS catalog preset ID.
workerIdYesLease owner identity.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.3.1
    • removedOutput schema / additionalProperties
      Removed value: -true
    • addedOutput schema / anyOf
      Added value: +[
+  {
+    "properties": {
+      "job": {
+        "type": "object"
+      }
+    },
+    "required": [
+      "job"
+    ],
+    "type": "object"
+  },
+  {
+    "properties": {
+      "error": {
+        "properties": {
+          "message": {
+            "type": "string"
+          },
+          "outcome": {
+            "enum": [
+              "unknown",
+              "not_executed"
+            ]
+          }
+        },
+        "required": [
+          "message",
+          "outcome"
+        ],
+        "type": "object"
+      }
+    },
+    "required": [
+      "error"
+    ],
+    "type": "object"
+  }
+]
  2. Changed2 schema fields changedv0.3.0
    • changedInput schema / properties / presetId / description
      Previous value: -"Stable NKS preset catalog ID."New value: +"NKS catalog preset ID."
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "type": "object"
+}
  3. Addedv0.2.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare the mutation profile (readOnly=false, destructive=true, idempotent=false), lowering the burden. The description adds the precondition that the lease must be unexpired and owned by the caller, which is real behavioral context, but it doesn't disclose the extension duration, failure behavior on an expired lease, or why the operation carries destructiveHint.

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?

A single front-loaded sentence with no filler or redundancy. Every clause (verb, resource, two preconditions) carries information.

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?

An output schema exists, so return values need not be explained, and the precondition for a successful call is stated. The main remaining gap is that the semantics of 'extend' (duration, idempotency implications) are left unstated, but this is minor for a two-parameter lease operation.

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%, so presetId and workerId are already documented in the schema, and the baseline is 3. The description only marginally enriches workerId by tying it to 'this worker' (the caller's identity); it adds no format or constraint detail beyond the schema.

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 ('Extend') and resource ('NKS generation lease') with scoping qualifiers ('unexpired', 'owned by this worker'). This clearly separates it from sibling lifecycle tools like claim_nks_generation_job, complete_nks_generation_job, and fail_nks_generation_job, though those siblings are not named.

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?

Usage is implied rather than stated: the 'unexpired' and 'owned by this worker' conditions suggest this is a keep-alive only the current lease holder should call, versus claim_/complete_/fail_ siblings. There is no explicit when-to-use or when-not-to-use guidance, so the agent must infer the lifecycle position.

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