Skip to main content
Glama
Sign In
cavi-ai

ableton-mcp

by cavi-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

get_beat_repeat_fill

Read-onlyIdempotent

Read a temporary Beat Repeat fill or list retained handles after reconnect. Reports native IDs, status, release checks, and cleanup errors; handles aren't saved in the Set.

Instructions

Read a temporary Repeat fill or list retained handles after reconnect. Reports current native IDs, status, Off observation, historical release verification and cleanup errors. Handles are not saved in the Set.

Input Schema

NameRequiredDescriptionDefault
fillIdNoFill ID from start or listing; omit to list.

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"
+          }
+        ]
+      },
+      "deviceId": {
+        "anyOf": [
+          {
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ]
+      },
+      "fillId": {
+        "type": "string"
+      },
+      "fills": {
+        "items": {
+          "type": "object"
+        },
+        "type": "array"
+      },
+      "finished": {
+        "type": "boolean"
+      },
+      "identityToken": {
+        "type": "string"
+      },
+      "reason": {
+        "anyOf": [
+          {
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ]
+      },
+      "setFingerprint": {
+        "type": "string"
+      },
+      "stateVersion": {
+        "minimum": 1,
+        "type": "integer"
+      },
+      "status": {
+        "type": "string"
+      },
+      "supported": {
+        "type": "boolean"
+      },
+      "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 that this is a read-only, idempotent, non-destructive operation. The description adds useful behavioral context beyond that: it reports native IDs, status, Off observation, historical release verification, cleanup errors, and notes that handles are not saved in the Set.

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 primary action, with no obvious filler. Some phrases such as 'Off observation' and 'historical release verification' are dense, but they are relevant rather than redundant.

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?

Given the low parameter complexity, full schema coverage, annotations, and an output schema, the definition contains enough information to invoke the tool correctly. The main missing context is explicit routing versus the related perform/finish and performance-context siblings.

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 one optional parameter with 100% schema description coverage, and the schema already explains 'Fill ID from start or listing; omit to list.' The description supports the same read-vs-list distinction but adds little parameter detail beyond the schema baseline.

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 read/list operation over temporary Repeat fills and retained handles, so the agent can identify the resource and basic action. It does not explicitly name the related perform/finish sibling tools, but the read-only retrieval purpose is clear.

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 'after reconnect' gives one usage context, and the schema says to omit fillId to list, implying two invocation modes. However, the description does not explicitly state when to use this versus perform_beat_repeat_fill, finish_beat_repeat_fill, or get_beat_repeat_performance_context.

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