Skip to main content
Glama
cavi-ai

ableton-mcp

by cavi-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

apply_midi_ratchet_pattern

Plan or apply MIDI ratchet patterns in Ableton Live, preserving velocity, probability, mute, release velocity, and deviation, with a guarded confirm-to-execute workflow.

Instructions

Plan or apply guarded MIDI ratchets while preserving velocity, probability, mute, release velocity, and velocity deviation.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
gateYesEach repeated note's duration as a fraction of its subdivision.
clipIdYesStable 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.
dryRunNoOmit or true to return a plan; false requires a valid confirmationToken.
noteIdsYesUnique stable note IDs at complete selected onsets.
trackIdYesStable track ID returned by list_tracks.
planHashNoHash returned by the matching dry run.
spanBeatsYesTotal beat span occupied by every selected onset's repeats.
repeatCountsYesRepeating ratchet count by ordered onset; 3 creates an exact triplet inside spanBeats.
confirmationTokenNoShort-lived, single-use token returned by the matching dry run.
expectedStateVersionYesExact stateVersion observed immediately before planning.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior4/5

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

Annotations only say non-readonly and non-destructive. The description adds that it preserves velocity, probability, mute, release velocity, and velocity deviation, and uses 'guarded' to hint at the confirmation flow, going beyond the annotations.

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?

A single concise sentence that front-loads the primary action and key constraints without unnecessary detail.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool with 10 parameters and a plan/apply guarded flow, the description lacks context on the two-phase process (dry run, confirmationToken, expectedStateVersion) and does not reference related tools. An agent would need to infer the flow from parameters.

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 covers all parameters with descriptions (100%). The tool description adds no additional parameter semantics beyond what the schema already provides, so baseline 3 applies.

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?

The description states a specific verb (plan or apply) and resource (MIDI ratchets) and lists the attributes preserved (velocity, probability, mute, release velocity, velocity deviation), clearly distinguishing it from other pattern tools by name and content.

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

Usage Guidelines2/5

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

No explicit guidance on when to use this tool versus its plan counterpart (plan_midi_ratchet_pattern) or other apply_midi_* tools. The description does not mention the dry-run/apply flow or exclusions.

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