Skip to main content
Glama

mcp_opendaw_create_melody_from_progression

Generates a lead melody from a chord progression, using chord tones on strong beats and passing tones on weak beats. Supports patterns: chord_tones, sustained, syncopated, triadic, stepwise.

Instructions

Create a lead melody from a chord progression string.

Completes the harmonic quartet: create_chord_pads (sustained harmony) + create_arpeggiated_progression (arp movement) + create_bass_from_progression (bass foundation) + THIS (lead melody). All four take the same "Am-F-C-G" string.

The melody hits chord tones on strong beats (1, 3) and uses passing tones or neighbor tones on weak beats (2, 4) for melodic interest.

pattern: Melodic pattern: "chord_tones" — root/third/fifth on beats 1+3, passing tone on 2+4 "sustained" — one chord tone per bar, held for full bar (ballad) "syncopated" — 8th notes, chord tones on downbeats, passing on ups "triadic" — arpeggiated 8ths through chord tones (folk, country) "stepwise" — scale steps between chord tones (pop, classical)

bars_per_chord: Bars per chord (default 4). octave: MIDI octave for melody (5 = C5=72, typical lead range). velocity: Note velocity (0-1, default 0.75). track_index: Track for melody (typically melody track = 3).

Example:

Pop lead from I-V-vi-IV

create_melody_from_progression("C-G-Am-F", pattern="chord_tones", octave=5, track_index=3)

Ballad sustained melody

create_melody_from_progression("Am-F-C-G", pattern="sustained", octave=5, bars_per_chord=4)

Country triadic fiddle

create_melody_from_progression("D-G-A-D", pattern="triadic", octave=5, velocity=0.8)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
octaveNo
patternNochord_tones
velocityNo
start_beatNo
unit_indexNo
progressionNoAm-F-C-G
track_indexNo
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 burden. It details the melody generation algorithm (chord/tonal pattern on strong beats, passing tones on weak) and explains each pattern's behavior. However, it doesn't disclose side effects like track creation/modification or return value format, missing some external aspects.

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?

The description is well-structured: purpose, context, algorithm, parameter details, and examples. Every sentence adds value with no redundancy or fluff, achieving clarity and efficiency.

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?

Despite 8 parameters and no annotation, the description covers purpose, usage timing, algorithm, parameter semantics, and provides examples. It is self-contained and complete for an agent to understand and invoke the tool correctly.

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 description coverage is 0%, but the description fully compensates by explaining every parameter's meaning, default values, and typical ranges (e.g., octave=5 for lead, pattern behaviors). Examples further clarify usage, adding high value 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 it creates a lead melody from a chord progression string, and explicitly distinguishes it from sibling tools by naming the harmonic quartet (create_chord_pads, create_arpeggiated_progression, create_bass_from_progression, THIS).

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 explains when to use this tool: as part of the harmonic quartet with shared input format. It provides context but doesn't explicitly state when not to use it or name alternative tools for melody creation (e.g., create_melody), though the quartet framing implies a specific purpose.

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