Skip to main content
Glama

mcp_opendaw_create_harmony_line

Generates a consonant harmony line from a melody by shifting notes by diatonic scale steps in a given key, ideal for vocal harmonies and counter-melodies.

Instructions

Create a harmony line from an existing melody using diatonic intervals.

Reads notes from a source melody and creates a parallel harmony line at a specified diatonic interval. The harmony stays in key — each note is shifted by N scale steps (not semitones), producing consonant harmony automatically.

Harmony intervals (diatonic):

  • third: +2 scale steps — the most common harmony (Lennon-McCartney, Everly Brothers, country duets). Sweet and consonant.

  • sixth: +5 scale steps — wider, jazzier. Creates open, airy harmony.

  • fifth: +4 scale steps — power harmony, medieval/organum sound.

  • fourth: +3 scale steps — suspended, ambiguous. Gregorian/modal.

  • octave: +7 scale steps (or -7) — doubling, not true harmony but useful for layering.

Essential for: vocal harmonies, string pads behind melody, guitar harmonies, counter-melody foundation, thickening lead lines.

source_unit/track/region: Location of the source melody. target_unit/track/region: Where to write the harmony. -1 = create new track/region automatically. interval: third, sixth, fifth, fourth, octave. root_note + scale: The key for diatonic interval calculation. The harmony notes are guaranteed to be in this scale. direction: "above" or "below" — place harmony above or below the melody. velocity_scale: Multiply source velocities by this (default 0.8 = harmony slightly quieter than melody).

Returns the created harmony notes.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
scaleNomajor
intervalNothird
directionNobelow
root_noteNoC
source_unitNo
target_unitNo
source_trackNo
target_trackNo
source_regionNo
target_regionNo
velocity_scaleNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

With no annotations, the description carries full burden. It explains the key behavior (reads melody, writes harmony, stays in key, can auto-create tracks) but does not mention potential side effects like overwriting existing targets or error conditions. It is adequate but not fully transparent.

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, mechanism, interval list with descriptions, use cases, parameter explanations. It is concise without unnecessary words, front-loads the core action, and uses markdown effectively for readability.

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 main behaviors (diatonic intervals, target auto-creation, velocity scaling) and includes musical context. It lacks explicit handling of edge cases (e.g., empty source, rests) but is sufficient for a tool with output schema and clear defaults. Sibling tools are differentiated well.

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?

Despite 0% schema coverage, the description explains the role of key parameters (source/target locations, interval, root_note+scale, direction, velocity_scale) with meaningful context (e.g., interval musical descriptions, default auto-create). It adds significant value beyond the schema defaults.

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 'Create a harmony line from an existing melody using diatonic intervals', specifying the action, input, and method. It distinguishes from siblings by focusing on parallel diatonic harmony, unlike other harmony tools.

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 (e.g., vocal harmonies, string pads) and outlines the intervals, but does not explicitly state when not to use it or provide alternatives. It gives good context but lacks exclusions.

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