Skip to main content
Glama
cavi-ai

ableton-mcp

by cavi-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

save_midi_feel_template

Capture exact MIDI note timing and velocity from a track clip into a named private template for reuse. Choose notes, grid, and cycle origin; existing templates are never overwritten.

Instructions

Analyze exact MIDI notes with an optional cycle origin and save a private named timing/velocity template. Never overwrites. Rejects assigned native grooves; does not capture their playback effects.

Input Schema

NameRequiredDescriptionDefault
barsNo
gridYes
nameYesNew local template name; letters, numbers, dot, underscore and hyphen only.
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": {
+      "name": {
+        "type": "string"
+      },
+      "path": {
+        "type": "string"
+      },
+      "template": {
+        "type": "object"
+      }
+    },
+    "required": [
+      "name",
+      "path",
+      "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.8/5.0
Behavior4/5

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

Annotations already establish this as a non-read-only, non-idempotent, non-destructive write. The description adds useful behavioral context beyond that: templates are private, never overwritten, and native groove playback effects are not captured. It does not detail duplicate-name behavior or failure modes, but the key mutation semantics are covered.

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 compact sentences with the primary action front-loaded. The subsequent constraints are short and each adds material information, with no filler.

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-value explanation is not required. For a 7-parameter mutation tool with annotations and mostly covered schema, the description supplies the critical constraints and caveats, though it could mention duplicate-name handling or what happens when no notes match.

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 description coverage is 71%, so the baseline is 3. The description reinforces the roles of noteIds and originBeats ('exact MIDI notes with an optional cycle origin') and notes the private named template, but adds little about grid, bars, or the distinction between clipId and trackId beyond what the schema already states.

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 names a specific verb and resource: analyze MIDI notes and save a named timing/velocity template. It distinguishes itself functionally from siblings like analyze_midi_feel and load_midi_feel_template by focusing on persistence, but does not explicitly name those alternatives.

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 tool is used to persist a template and states an exclusion: assigned native grooves are rejected. It does not explicitly direct the agent to analyze_midi_feel for inspection-only work or explain when to choose this over other groove-related tools.

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