Skip to main content
Glama

mcp_opendaw_create_chord_pads

Generates sustained chord pads from a simple hyphen-separated chord progression string (e.g., 'Am-F-C-G') with configurable octave, velocity, and bars per chord.

Instructions

Create chord pads from a human-readable progression string.

Unlike create_chord_progression (which takes JSON arrays), this takes a simple hyphen-separated string like "Am-F-C-G" — much easier for agents and humans to write. Generates sustained chord pads with configurable octave, velocity, and bars per chord.

progression: Hyphen-separated chords. Each chord is root+type: "Am" = A minor, "F" = F major, "Cmaj7" = C major seventh, "G7" = G dominant 7, "Dm7" = D minor 7, "Esus4" = E suspended 4. Supported types: maj, min, dom7, maj7, min7, sus2, sus4, add9, dim, aug. Default "Am-F-C-G" = i-VI-III-VII in A minor (synthwave/trance). "C-Am-F-G" = I-vi-IV-V in C major (pop). "Dm7-G7-Cmaj7-Am7" = ii-V-I-vi in C (jazz).

bars_per_chord: How many bars each chord lasts (default 4 = one chord per 4-bar phrase). 2 = faster changes, 8 = slow pads.

octave: MIDI octave for chord voicing (3 = C3=48, typical pad range). velocity: Note velocity (0-1, default 0.65 = soft pad). unit_index: AU index with note tracks. track_index: Track for chord pads (typically harmony track = 2). start_beat: Where the progression starts. note_duration: Note length in beats (default 3.8 = almost full bar with small gap for articulation).

Returns chords created, pitches per chord, total notes.

Example:

i-VI-III-VII in A minor (synthwave pads)

create_chord_progression("Am-F-C-G", bars_per_chord=4, octave=3)

ii-V-I-vi in C (jazz comping under)

create_chord_progression("Dm7-G7-Cmaj7-Am7", bars_per_chord=2, octave=3)

I-V-vi-IV in C (pop progression)

create_chord_progression("C-G-Am-F", bars_per_chord=4, octave=4, track_index=2, velocity=0.6)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
octaveNo
velocityNo
start_beatNo
unit_indexNo
progressionNoAm-F-C-G
track_indexNo
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 responsibility. It explains the tool creates sustained chord pads with configurable parameters, describes return values (chords created, pitches, total notes), and covers default behaviors. However, it does not mention potential side effects or performance implications, which would elevate the score to 5.

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 summary, parameter explanations, and examples. It front-loads the key differentiator and purpose. While comprehensive, it is slightly verbose but each sentence adds value. A score of 4 reflects good economy without being terse.

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

Completeness5/5

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

Given the tool has 8 parameters, no annotations, and a complex harmonic domain, the description is remarkably complete. It covers input format, parameter roles, defaults, supported chord types, use case examples, and return values. The presence of an output schema is noted, and the description adequately explains what is returned.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, but the description adds extensive meaning for each parameter. It details the chord format (root+type), supported types (maj, min, dom7, etc.), explains bars_per_chord, octave, velocity, and other parameters with default values and examples. This fully compensates for the lack of schema descriptions.

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 creates chord pads from a human-readable progression string. It explicitly distinguishes from the sibling tool create_chord_progression by contrasting the input format (hyphen-separated string vs JSON arrays). The verb and resource are specific and unambiguous.

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

Usage Guidelines5/5

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

The description provides explicit guidance on when to use this tool versus the alternative create_chord_progression, noting that this tool is for simpler string inputs. It also gives genre-specific examples (synthwave, pop, jazz) and explains default behaviors, helping the agent decide contextually.

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