Skip to main content
Glama
cavi-ai

ableton-mcp

by cavi-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

capture_group_system_snapshot

Read-onlyIdempotent

Captures an existing Group Track, nested groups, and all descendant tracks in Live order as persistable JSON, with every snapshot matching one state version for reliable read-only hierarchy export.

Instructions

Capture an existing Group Track, nested groups and all descendant tracks in Live order as persistable JSON. Every track snapshot and the final hierarchy must match one state version. Read-only; does not save clips, samples, hidden plug-in state, automation or mappings, or create/recall tracks.

Input Schema

NameRequiredDescriptionDefault
busTrackIdYesID from list_tracks.

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": {
+      "busTrackId": {
+        "type": "string"
+      },
+      "limitation": {
+        "type": "string"
+      },
+      "snapshot": {
+        "type": "object"
+      },
+      "stateVersion": {
+        "minimum": 1,
+        "type": "integer"
+      }
+    },
+    "required": [
+      "stateVersion",
+      "busTrackId",
+      "snapshot",
+      "limitation"
+    ],
+    "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 / busTrackId / description
      Previous value: -"Stable track ID returned by list_tracks."New value: +"ID from list_tracks."
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "type": "object"
+}
  3. Addedv0.2.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent and non-destructive, but the description adds real context beyond them: it enumerates exactly what state is excluded (clips, samples, hidden plug-in state, automation, mappings) and asserts the atomicity guarantee that every track snapshot and the hierarchy must match one state version. That is useful behavioral disclosure not present in the structured fields.

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 tight sentences with zero redundancy. The positive definition (what is captured, in what order, as what) leads, and the read-only/exclusion caveats follow, making it well front-loaded.

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 annotations covering the safety profile, an output schema handling return values, and full parameter documentation, the description only needs to add scope and exclusions, which it does. A brief pointer to the paired save/recall tools would make it self-sufficient, but nothing essential is missing.

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?

There is a single parameter with 100% schema coverage, and the schema already explains it ('ID from list_tracks'). The description adds no further meaning about busTrackId, so the baseline of 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?

The description states a specific verb (capture) and resource (an existing Group Track, nested groups and all descendant tracks) and adds the output form (persistable JSON in Live order). It implicitly separates itself from save/load/recall siblings by naming 'capture', but it does not explicitly contrast with the similar capture_track_state_snapshot, so it falls just short of a 5.

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 description gives negative scoping ('read-only; does not save clips, samples, hidden plug-in state, automation or mappings, or create/recall tracks'), which tells the agent what this is not. However, it never states when to prefer it over capture_track_state_snapshot or how it feeds save_group_system_snapshot/recall_group_system_snapshot, leaving usage largely implied.

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