Skip to main content
Glama

mcp_opendaw_create_voice_led_progression

Creates chord pads with smooth voice leading by re-voicing chords to minimize note movement, keeping common tones stationary and resolving others by nearest semitone step.

Instructions

Create chord pads with smooth voice leading — minimal movement between chords.

Unlike create_chord_pads (which voices every chord in root position causing large jumps), this tool re-voices each chord so individual voices move as little as possible. Common tones stay stationary, other voices resolve by nearest semitone step. The result: strings/pads that glide instead of jump.

progression: Hyphen-separated chords (same format as create_chord_pads). "Am-F-C-G" = i-VI-III-VII in A minor. "C-Am-F-G" = I-vi-IV-V in C major. "Dm7-G7-Cmaj7-Am7" = ii-V-I-vi in C (jazz).

bars_per_chord: Bars per chord (default 4). octave: Center octave for voicing range (3 = C3-C4 register, typical pads). velocity: Note velocity (0-1, default 0.65). unit_index: AU index with note tracks. track_index: Track for chord pads (typically 2 = harmony). start_beat: Where the progression starts. note_duration: Sustain length in beats (default 3.8 = near-full bar). voice_range: Max semitone span from center pitch for each voice (default 12 = one octave either side of center). Prevents voices from drifting too high or low. 7 = tighter, 18 = wider range.

Returns chord voicings, voice movements, and total notes.

Voice leading algorithm:

  1. First chord: root-position voicing centered on octave.

  2. For each subsequent chord: a. Find all pitch-class rotations/inversions of the chord. b. For each candidate voicing, compute total voice movement (sum of semitone distances from previous voicing, by voice index). c. Pick the voicing with minimal total movement. d. Constraint: each voice stays within ±voice_range of center.

  3. Common tones naturally stay (distance 0 = optimal).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
octaveNo
velocityNo
start_beatNo
unit_indexNo
progressionNoAm-F-C-G
track_indexNo
voice_rangeNo
note_durationNo
bars_per_chordNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

With no annotations, the description carries full behavioral transparency. It details the voice-leading algorithm step-by-step, explains constraints like voice_range, and describes the return value (chord voicings, voice movements, total notes). However, it does not explicitly mention side effects (e.g., overwriting existing notes) or any prerequisites.

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 well-structured with a clear opening, comparison, parameter list, and algorithm explanation. It is somewhat verbose, but every section adds value, especially the algorithm details. Almost no redundant information.

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?

The description covers the tool's behavior thoroughly, including the algorithm and parameter explanations. With 9 parameters and no required ones, it provides sufficient context. It does not discuss error handling or edge cases, and the output schema is present (so return format not needed). Slightly incomplete but good overall.

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?

The schema has 0% description coverage, so the description must explain parameters. It does so for all major parameters: progression (with examples), bars_per_chord, octave, velocity, note_duration, voice_range. Unit_index and track_index are mentioned but not deeply explained (though they are common). Overall, the description adds significant meaning beyond the schema.

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 clearly states the tool's purpose: creating chord pads with smooth voice leading. It uses the specific verb 'create' and resource 'chord pads with smooth voice leading'. It distinguishes itself from the sibling tool 'create_chord_pads' by explicitly contrasting its behavior (minimal movement) with root-position voicing.

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?

The description explicitly compares to 'create_chord_pads', stating when to use this tool (when smooth voice leading is desired) and when to use the alternative (root-position chords). It does not provide explicit 'when not to use' guidance, but the context is clear enough for an agent to decide.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/AMEOBIUS-team/opendaw-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server