Skip to main content
Glama
cavi-ai

ableton-mcp

by cavi-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

plan_group_system_recall

Read-onlyIdempotent

Validate a saved group-system snapshot by checking a one-to-one mapping to current Live tracks, ensuring matching order and group hierarchy for guarded recall.

Instructions

Read a saved group-system capture and check a one-to-one mapping onto existing tracks in matching Live order and group hierarchy. Validates each exposed track state for individual guarded recall; does not mutate Live or perform a multi-track transaction.

Input Schema

NameRequiredDescriptionDefault
nameYesExact saved group-system snapshot name.
mappingYesOne explicit source-to-target entry for every saved track.
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"
+      },
+      "dryRun": {
+        "const": true
+      },
+      "limitation": {
+        "type": "string"
+      },
+      "stateVersion": {
+        "minimum": 1,
+        "type": "integer"
+      },
+      "tracks": {
+        "items": {
+          "type": "object"
+        },
+        "type": "array"
+      }
+    },
+    "required": [
+      "stateVersion",
+      "dryRun",
+      "busTrackId",
+      "tracks",
+      "limitation"
+    ],
+    "type": "object"
+  },
+  {
+    "properties": {
+      "error": {
+        "properties": {
+          "message": {
+            "type": "string"
+          },
+          "outcome": {
+            "enum": [
+              "unknown",
+              "not_executed"
+            ]
+          }
+        },
+        "required": [
+          "message",
+          "outcome"
+        ],
+        "type": "object"
+      }
+    },
+    "required": [
+      "error"
+    ],
+    "type": "object"
+  }
+]
  2. Changed4 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."
    • changedInput schema / properties / mapping / items / properties / sourceTrackId / description
      Previous value: -"Stable track ID returned by list_tracks."New value: +"ID from list_tracks."
    • changedInput schema / properties / mapping / items / properties / targetTrackId / 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.9/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. The description adds useful context by stating that it validates each exposed track state for individual guarded recall and explicitly clarifies that it does not perform a multi-track transaction.

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 two tight sentences, front-loads the core action, and contains no redundant or filler text. Every sentence contributes to understanding the tool's purpose and boundaries.

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?

The tool has an output schema and complete parameter descriptions, so return values do not need explanation here. The description covers validation behavior and non-mutation, though it could be slightly stronger with explicit usage prerequisites.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3. The description adds meaningful constraints for the mapping parameter: the mapping must be one-to-one onto existing tracks and match Live order and group hierarchy, which goes beyond the schema's per-item source/target descriptions.

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 and resource: reading a saved group-system capture and checking a one-to-one mapping onto existing tracks. It does not name sibling tools such as recall_group_system_recall directly, but the contrast with mutation is clear from 'does not mutate Live or perform a multi-track transaction.'

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 implies this is a planning/validation step before guarded recall, but it does not explicitly say when to use it versus alternatives like recall_group_system_recall. The only explicit exclusion is that it does not mutate Live or perform a multi-track transaction.

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