Skip to main content
Glama
cavi-ai

ableton-mcp

by cavi-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

get_arrangement_take

Read-onlyIdempotent

Retrieve an Arrangement recording handle to inspect clip spans, range coverage, and control ownership, or list retained handles after a lost reply.

Instructions

Read one Arrangement recording handle, new clip spans, range coverage and control ownership, or list handles after a lost reply. Start acceptance and range coverage do not prove recorded performance, audio-file finalization or sound. Handles last until release or bridge restart; all profile.

Input Schema

NameRequiredDescriptionDefault
takeIdNoRuntime take ID; omit to list retained handles.

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": {
+      "cleanupErrors": {
+        "items": {
+          "type": "string"
+        },
+        "type": "array"
+      },
+      "clipId": {
+        "anyOf": [
+          {
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ]
+      },
+      "clips": {
+        "items": {
+          "type": "object"
+        },
+        "type": "array"
+      },
+      "deviceId": {
+        "anyOf": [
+          {
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ]
+      },
+      "endBeats": {
+        "type": "number"
+      },
+      "identityToken": {
+        "type": "string"
+      },
+      "performanceVerified": {
+        "type": "boolean"
+      },
+      "reason": {
+        "anyOf": [
+          {
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ]
+      },
+      "recordingRequested": {
+        "type": "boolean"
+      },
+      "recordingVerified": {
+        "type": "boolean"
+      },
+      "setFingerprint": {
+        "type": "string"
+      },
+      "startBeats": {
+        "type": "number"
+      },
+      "stateVersion": {
+        "minimum": 1,
+        "type": "integer"
+      },
+      "status": {
+        "type": "string"
+      },
+      "supported": {
+        "type": "boolean"
+      },
+      "takeId": {
+        "type": "string"
+      },
+      "takes": {
+        "items": {
+          "type": "object"
+        },
+        "type": "array"
+      },
+      "trackId": {
+        "type": "string"
+      }
+    },
+    "required": [
+      "stateVersion"
+    ],
+    "type": "object"
+  },
+  {
+    "properties": {
+      "error": {
+        "properties": {
+          "message": {
+            "type": "string"
+          },
+          "outcome": {
+            "enum": [
+              "unknown",
+              "not_executed"
+            ]
+          }
+        },
+        "required": [
+          "message",
+          "outcome"
+        ],
+        "type": "object"
+      }
+    },
+    "required": [
+      "error"
+    ],
+    "type": "object"
+  }
+]
  2. Addedv0.3.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already establish read-only, idempotent, non-destructive behavior, so the description appropriately adds context about handle lifetime and semantic limits: handles last until release or bridge restart, and acceptance/range coverage do not prove recorded performance, audio finalization, or sound. This is useful behavioral guidance beyond the annotations.

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?

The description is short and front-loads the read/list purpose before the caveats. The phrase 'all profile' is somewhat cryptic, but the overall structure is efficient and no sentence is clearly wasted.

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 and annotations covering safety, the description provides enough context about handle state, listing behavior, and lifetime caveats for an agent to call the tool correctly. The remaining gaps are minor, mainly the lack of explicit sibling routing.

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%, and the takeId description already explains that omitting it lists retained handles. The tool description mirrors that behavior but adds no extra syntax or format detail, so the baseline of 3 is appropriate.

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?

The description clearly states a read operation on an Arrangement recording handle and mentions listing retained handles, which separates it from write-oriented siblings like record_arrangement_take and finish_arrangement_take. It does not explicitly name those siblings, so it stops short of true sibling differentiation.

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 'or list handles after a lost reply' gives one concrete usage scenario, but the description does not explicitly say when to use this instead of record_arrangement_take, finish_arrangement_take, or audition_arrangement_passage. Usage is implied rather than fully guided.

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