Skip to main content
Glama
cavi-ai

ableton-mcp

by cavi-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

analyze_midi_feel

Read-onlyIdempotent

Measures stored MIDI timing and velocity per grid slot over up to 8 clip-meter bars to quantify rhythmic feel, with optional note filtering and cycle origin.

Instructions

Measure stored MIDI timing/velocity by grid slot over 1–8 clip-meter bars, with optional exact notes and cycle origin. Defaults: all notes, beat zero. Read-only; assigned native groove playback is not measured or extracted.

Input Schema

NameRequiredDescriptionDefault
barsNoNumber of clip-meter bars in the repeating analysis cycle; defaults to one.
gridYes
clipIdYeslist_clips Session ID or supported list_arrangement_clips ID.
noteIdsNoExact source note IDs; omitted means all stored notes.
trackIdYesID from list_tracks.
originBeatsNoClip-beat cycle origin; defaults to zero. Use an observed loop start when intended.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.3.1
    • changedInput schema / properties / clipId / description
      Previous value: -"Session ID from list_clips; Arrangement ID from list_arrangement_clips where supported."New value: +"list_clips Session ID or supported list_arrangement_clips ID."
    • removedOutput schema / additionalProperties
      Removed value: -true
    • addedOutput schema / anyOf
      Added value: +[
+  {
+    "properties": {
+      "bars": {
+        "type": "integer"
+      },
+      "clipId": {
+        "type": "string"
+      },
+      "grid": {
+        "type": "string"
+      },
+      "notes": {
+        "items": {
+          "type": "object"
+        },
+        "type": "array"
+      },
+      "originBeats": {
+        "type": "number"
+      },
+      "slots": {
+        "items": {
+          "type": "object"
+        },
+        "type": "array"
+      },
+      "sourceNoteCount": {
+        "type": "integer"
+      },
+      "stateVersion": {
+        "minimum": 1,
+        "type": "integer"
+      },
+      "template": {
+        "type": "object"
+      },
+      "totalSourceNoteCount": {
+        "type": "integer"
+      },
+      "trackId": {
+        "type": "string"
+      }
+    },
+    "required": [
+      "stateVersion",
+      "trackId",
+      "clipId",
+      "grid",
+      "bars",
+      "originBeats",
+      "sourceNoteCount",
+      "totalSourceNoteCount",
+      "notes",
+      "slots",
+      "template"
+    ],
+    "type": "object"
+  },
+  {
+    "properties": {
+      "error": {
+        "properties": {
+          "message": {
+            "type": "string"
+          },
+          "outcome": {
+            "enum": [
+              "unknown",
+              "not_executed"
+            ]
+          }
+        },
+        "required": [
+          "message",
+          "outcome"
+        ],
+        "type": "object"
+      }
+    },
+    "required": [
+      "error"
+    ],
+    "type": "object"
+  }
+]
  2. Changed5 schema fields changedv0.3.0
    • changedInput schema / properties / clipId / description
      Previous value: -"Stable clip ID: track-N:clip-M from list_clips, or track-N:arrangement-clip-M from list_arrangement_clips for tools that support Arrangement clips."New value: +"Session ID from list_clips; Arrangement ID from list_arrangement_clips where supported."
    • addedInput schema / properties / noteIds
      Added value: +{
+  "description": "Exact source note IDs; omitted means all stored notes.",
+  "items": {
+    "type": "integer"
+  },
+  "maxItems": 4096,
+  "minItems": 1,
+  "type": "array",
+  "uniqueItems": true
+}
    • addedInput schema / properties / originBeats
      Added value: +{
+  "description": "Clip-beat cycle origin; defaults to zero. Use an observed loop start when intended.",
+  "minimum": 0,
+  "type": "number"
+}
    • changedInput schema / properties / trackId / 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 carry readOnly, idempotent, non-destructive and closed-world, and the description reinforces 'Read-only' consistently. It adds genuine value beyond the annotations by clarifying the scope boundary that 'assigned native groove playback is not measured or extracted', which is not derivable from 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?

Three compact clauses front-load the core action, then defaults, then the read-only/scope caveat. Every segment carries information and nothing is repeated from the schema or annotations.

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?

An output schema exists so return values need not be described, and annotations cover the safety profile; the description supplies scope, defaults, and the crucial stored-vs-native-groove exclusion. The only gap is the absence of guidance on choosing this tool over its analysis siblings.

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?

With 83% schema coverage the baseline is 3, but the description meaningfully synthesizes several parameters: the 1-8 bar range, optional exact notes (noteIds), and cycle origin (originBeats), plus defaults. The grid enum values are left to the schema, which is fine, though no extra semantic detail is added there.

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?

States a specific verb (measure) and resource (stored MIDI timing/velocity) scoped by grid slot and clip-meter bar range, which is far more precise than a tautology. It does not name or differentiate itself from close siblings such as analyze_midi_parts or analyze_midi_clip_scale, leaving the agent to infer which analysis applies.

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 the analysis context ('stored MIDI', 'beat zero' default) and scopes out native groove playback, but never states when to reach for this tool versus alternatives like get_clip_groove_context or inspect_clip_groove_postconditions. Usage is inferrable from the scope statement rather than explicit.

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