Skip to main content
Glama

mcp_opendaw_create_counter_melody_from_progression

Generate a secondary melodic line (counter-melody) from a chord progression, adding harmonic depth and contrapuntal interest without competing with the main melody.

Instructions

Create a counter-melody (second melodic line) from a chord progression.

A counter-melody is a secondary melodic line that plays alongside the primary melody. It provides harmonic depth and contrapuntal interest without competing for the listener's attention.

This completes the harmonic quintet: chord_pads + arpeggiated_progression + bass_from_progression + melody_from_progression + THIS (counter-melody). Place on track 4 (default) to avoid clashing with melody (track 3).

pattern: Contrapuntal pattern: "contrary" — moves opposite to chord root motion (if root goes up, counter goes down). Classic species-1 counterpoint feel. "oblique" — one note sustained across the chord, changes only when the harmony forces it. Minimalist, drone-like. "parallel_third" — parallels the chord tones a third above. Sweet, consonant, pop/folk counter-melody. "parallel_sixth" — parallels the chord tones a sixth above. Open, spacious, cinematic. More independent than parallel third. "call_response" — answers after the melody would play: rests on beats 1-2, plays on beats 3-4. Antiphonal, gospel/soul feel.

bars_per_chord: Bars per chord (default 4). octave: MIDI octave (default 4 = below typical melody at 5). velocity: Lower than melody (0-1, default 0.6 = supportive, not competing). track_index: Track for counter-melody (default 4, above melody track 3).

Example:

Counter-melody below the lead

create_counter_melody_from_progression("Am-F-C-G", pattern="contrary", octave=4, velocity=0.6)

Cinematic parallel sixths

create_counter_melody_from_progression("Dm-G-C-Am", pattern="parallel_sixth", octave=4, velocity=0.55)

Gospel call-and-response

create_counter_melody_from_progression("C-Am-Dm-G", pattern="call_response", octave=5, velocity=0.65)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
octaveNo
patternNocontrary
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?

No annotations provided, so the description carries the full burden. It discloses that the tool places the counter-melody on track 4 by default to avoid clashing with melody, that velocity should be lower than melody, and describes five contrapuntal patterns. It does not mention return values, but the output schema exists. Overall, good behavioral disclosure for a creation tool.

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 with a definition, explanation of patterns, parameter descriptions, and examples. It is front-loaded with purpose and uses bullet-like formatting for patterns. Every sentence adds value; no redundancy. Concise yet comprehensive.

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?

Given the tool's complexity (8 parameters, no annotations, and a large sibling list), the description provides sufficient context. It explains the musical role, track placement, pattern variations, and parameter usage. The output schema exists but is not described, which is acceptable. The description is 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.

Parameters4/5

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

Schema description coverage is 0%, but the description compensates by explaining the pattern options in detail, providing defaults and ranges for velocity, octave, bars_per_chord, and track_index. However, parameters start_beat and unit_index are not mentioned in the description. The examples illustrate usage for progression. Strong coverage for most parameters.

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 counter-melody from a chord progression. It distinguishes itself from similar tools by placing it in a quintet of harmonic tools and specifying track placement to avoid clashes with melody. The verb 'create' and resource 'counter_melody' are specific.

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 provides context for when to use: as part of a harmonic quintet and on a specific track. It explains the role of the counter-melody relative to melody and bass. However, it does not explicitly state when not to use or list alternatives, but the quintet positioning and pattern descriptions imply usage scenarios.

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