Skip to main content
Glama
cavi-ai

ableton-mcp

by cavi-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

get_producer_chain_blueprint

Read-onlyIdempotent

Retrieve one ordered Ableton factory-device chain or shared-bus topology by target ID, including exact browser paths, stage roles, execution tools, and limitations.

Instructions

Return one ordered factory-device chain or shared-bus topology with exact browser paths, stage roles, execution tools, and explicit limitations.

Input Schema

NameRequiredDescriptionDefault
targetYesExact blueprint ID returned by list_producer_chain_blueprints.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.3.1
    • removedOutput schema / additionalProperties
      Removed value: -true
    • addedOutput schema / anyOf
      Added value: +[
+  {
+    "properties": {
+      "blueprint": {
+        "properties": {
+          "id": {
+            "type": "string"
+          },
+          "summary": {
+            "type": "string"
+          },
+          "topology": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "id",
+          "topology",
+          "summary"
+        ],
+        "type": "object"
+      }
+    },
+    "required": [
+      "blueprint"
+    ],
+    "type": "object"
+  },
+  {
+    "properties": {
+      "error": {
+        "properties": {
+          "message": {
+            "type": "string"
+          },
+          "outcome": {
+            "enum": [
+              "unknown",
+              "not_executed"
+            ]
+          }
+        },
+        "required": [
+          "message",
+          "outcome"
+        ],
+        "type": "object"
+      }
+    },
+    "required": [
+      "error"
+    ],
+    "type": "object"
+  }
+]
    • removedOutput schema / properties
      Removed value: -{
-  "blueprint": {
-    "additionalProperties": true,
-    "properties": {
-      "id": {
-        "type": "string"
-      },
-      "summary": {
-        "type": "string"
-      },
-      "topology": {
-        "type": "string"
-      }
-    },
-    "required": [
-      "id",
-      "topology",
-      "summary"
-    ],
-    "type": "object"
-  }
-}
    • removedOutput schema / required
      Removed value: -[
-  "blueprint"
-]
  2. Changed2 schema fields changedv0.3.0
    • addedInput schema / properties / target / description
      Added value: +"Exact blueprint ID returned by list_producer_chain_blueprints."
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "properties": {
+    "blueprint": {
+      "additionalProperties": true,
+      "properties": {
+        "id": {
+          "type": "string"
+        },
+        "summary": {
+          "type": "string"
+        },
+        "topology": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "id",
+        "topology",
+        "summary"
+      ],
+      "type": "object"
+    }
+  },
+  "required": [
+    "blueprint"
+  ],
+  "type": "object"
+}
  3. Changed1 schema field changedv0.2.0
    • changedInput schema / properties / target / enum
      Previous value: -[
-  "bass",
-  "drums",
-  "vocals",
-  "guitar",
-  "keys",
-  "synth",
-  "mix-bus",
-  "mastering",
-  "reverb-return",
-  "delay-return",
-  "layered-bass-system",
-  "layered-synth-system"
-]New value: +[
+  "bass",
+  "drums",
+  "vocals",
+  "guitar",
+  "keys",
+  "synth",
+  "mix-bus",
+  "mastering",
+  "reverb-return",
+  "delay-return",
+  "layered-bass-system",
+  "layered-synth-system",
+  "layered-drums-system",
+  "layered-keys-system",
+  "layered-vocals-system",
+  "layered-guitar-system"
+]
  4. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world, so the safety profile is covered. The description adds the content shape (ordered chain, stage roles, execution tools, limitations), but says nothing about failure behavior for an unknown target ID or whether 'explicit limitations' means caveats about the blueprint versus unsupported targets.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One dense, front-loaded sentence with no filler and the object of the return stated up front. It is slightly overloaded by enumerating four payload facets, but nothing is wasted.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a one-param lookup with a full output schema and complete annotations, the description covers enough to invoke it, but it leaves the agent without routing guidance among the several closely named producer-chain/inspect siblings, which is the main remaining risk.

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% and the single enum parameter is fully documented as 'Exact blueprint ID returned by list_producer_chain_blueprints'. The description supplies no additional parameter meaning, so baseline 3 applies.

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?

A specific verb ('Return') and resource ('one ordered factory-device chain or shared-bus topology') are stated, along with what the payload contains (browser paths, stage roles, execution tools, limitations). It is clear what the tool produces, though it never names the sibling list_producer_chain_blueprints that produces the IDs, so the enumeration-vs-single-fetch distinction is only implied by the verb.

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

Usage Guidelines2/5

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

No when-to-use, when-not-to-use, or alternatives are given. Nothing tells the agent to call list_producer_chain_blueprints first or how this differs from inspect_producer_chain / inspect_producer_bus, which sit adjacent in the sibling list and sound like overlapping read tools.

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