Skip to main content
Glama
cavi-ai

ableton-mcp

by cavi-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

analyze_midi_parts

Read-onlyIdempotent

Read 1-8 Session/Arrangement clips together to report per-part register, duration-weighted pitch classes, and combined diatonic compatibility.

Instructions

Read 1-8 explicit Session/Arrangement clips together. Report per-part register, duration-weighted pitch classes and combined diatonic compatibility. Loop/marker ranges only; not simultaneous playback or detected key. Audio, drums, recording and oversized clips are excluded explicitly. No edits or focus changes.

Input Schema

NameRequiredDescriptionDefault
partsYesExact parts from list_clips or list_arrangement_clips; unique references, at most 16384 analyzed notes total.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.3.1
    • changedInput schema / properties / parts / items / 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": {
+      "parts": {
+        "items": {
+          "type": "object"
+        },
+        "type": "array"
+      },
+      "stateVersion": {
+        "minimum": 1,
+        "type": "integer"
+      }
+    },
+    "required": [
+      "stateVersion",
+      "parts"
+    ],
+    "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

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the bar is lower; the description adds substantive context beyond them — the analysis outputs (per-part register, duration-weighted pitch classes, combined diatonic compatibility) and the hard input restrictions (audio/drums/recording/oversized excluded, loop/marker ranges only). "No edits or focus changes" largely restates readOnlyHint but reinforces it rather than contradicting.

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?

Four dense sentences, front-loaded with the core action and followed by output summary, exclusions, and safety note. Every sentence carries information, though the final "No edits or focus changes" is mildly redundant against the 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 spelled out, and annotations cover the safety profile. The description fills the remaining gaps — scope, exclusions, and analysis nature — leaving only minor omissions like pagination/size behavior, which is already bounded by the schema's note count.

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 single `parts` parameter is fully documented in the schema itself. The description's "1-8 explicit clips" mirrors the schema's minItems/maxItems rather than adding new syntax or format detail, so the baseline 3 applies when the schema does the heavy lifting.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb-plus-resource ("Read 1-8 explicit Session/Arrangement clips together... Report per-part register, duration-weighted pitch classes and combined diatonic compatibility") that distinguishes it from single-clip analyzers like analyze_midi_clip_scale or analyze_midi_clip_chords. It also explicitly excludes adjacent scopes ("not simultaneous playback or detected key"), so an agent can tell what this tool is not.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives clear context and exclusions: "Loop/marker ranges only," "Audio, drums, recording and oversized clips are excluded explicitly." It does not name a sibling alternative by name (e.g. analyze_midi_clip_scale for one clip), so routing between tools is left partly to inference.

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