Skip to main content
Glama
cavi-ai

ableton-mcp

by cavi-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

get_nks_generation_status

Read-onlyIdempotent

Read preset and durable job counts for a product, including pilot, gate, and queueable status for Serum 2 and Omnisphere, without creating a queue or contacting Live.

Instructions

Read discovered preset and durable job counts for one product. Serum 2 and Omnisphere also report pilot size, validated count, gate state, queueable factory count (including already queued presets), remaining discovered pilot IDs, and unqueued discovered pilot IDs without a durable job. Does not create a queue or contact Live.

Input Schema

NameRequiredDescriptionDefault
productSlugYesExact product slug.

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": {
+      "eligible": {
+        "type": "integer"
+      },
+      "fingerprint": {
+        "type": "string"
+      },
+      "initialized": {
+        "type": "boolean"
+      },
+      "jobs": {
+        "type": "object"
+      },
+      "productSlug": {
+        "type": "string"
+      }
+    },
+    "required": [
+      "productSlug",
+      "eligible",
+      "fingerprint",
+      "initialized",
+      "jobs"
+    ],
+    "type": "object"
+  },
+  {
+    "properties": {
+      "error": {
+        "properties": {
+          "message": {
+            "type": "string"
+          },
+          "outcome": {
+            "enum": [
+              "unknown",
+              "not_executed"
+            ]
+          }
+        },
+        "required": [
+          "message",
+          "outcome"
+        ],
+        "type": "object"
+      }
+    },
+    "required": [
+      "error"
+    ],
+    "type": "object"
+  }
+]
  2. Changed1 schema field changedv0.3.0
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "type": "object"
+}
  3. Addedv0.2.0

TDQS

A4.5/5.0
Behavior4/5

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

While annotations cover safety (`readOnlyHint: true`), the description provides valuable functional context regarding the data returned (e.g., 'queueable factory count', 'remaining discovered pilot IDs'). Furthermore, explicitly stating that it does not contact Live adds a necessary behavioral boundary not found in the schema or hints.

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?

The description is highly efficient, using two concise sentences to define the primary function, list the breadth of the data, and set critical operational boundaries. Every word contributes necessary functional information.

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?

Given that the tool is a status checker and provides a detailed enumeration of the specific data categories and fields it returns, the description is complete enough for an AI agent to confidently determine if this tool can satisfy a request for a status update on an NKS generation job.

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?

With schema description coverage at 100% and only one required parameter, the baseline score of 3 is appropriate. The description simply reinforces the requirement that the status is retrieved 'for one product,' which is already captured by the parameter description.

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 tool's purpose is to 'Read discovered preset and durable job counts' for a single product. It distinguishes its scope by listing specific metrics (pilot size, validated count, etc.) and naming specific product lines (Serum 2 and Omnisphere), allowing agents to precisely match user intent.

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

Usage Guidelines5/5

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

It provides crucial usage guidance by explicitly stating what the tool does not do: 'Does not create a queue or contact Live.' This immediately prevents the agent from invoking the tool when the user intends to start a process or interact with the live environment.

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