Skip to main content
Glama

mcp_opendaw_reharmonize_progression

Reharmonize chord progressions by substituting chords with functionally equivalent alternatives using techniques like tritone substitution, secondary dominants, and modal interchange.

Instructions

Reharmonize a chord progression — substitute chords with functionally equivalent alternatives for richer harmony.

Reharmonization is the art of replacing chords while preserving (or enhancing) the harmonic function. This tool applies classical and jazz substitution techniques to transform a progression without changing its fundamental direction.

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.

technique: Substitution technique:

  • "tritone_sub" — Replace V7 with ♭II7 (Db7 for G7). Guide tones (3rd+7th) are shared, creates chromatic bass motion. Jazz standard.

  • "secondary_dominant" — Insert V7 of the target chord before it. e.g. before Am → insert E7 (V7 of Am). Adds forward motion.

  • "diatonic_sub" — Replace with functionally equivalent diatonic chord. I→iii or I→vi (submediant), IV→ii (supertonic). Shares tones.

  • "modal_interchange" — Borrow chords from parallel key (minor↔major). In major: ♭VI, ♭III, ♭VII from natural minor. In minor: IV, II from major. Adds color and emotional depth.

  • "passing_dim" — Insert diminished passing chord for chromatic bass motion between chords a whole step apart. Creates smooth bass lines.

intensity: How many chords to substitute:

  • "light" — substitute 1 chord (the most impactful)

  • "medium" — substitute ~30% of eligible chords

  • "heavy" — substitute all eligible chords

target_chord: Index of specific chord to substitute (0-based). -1 = auto select. Only used for tritone_sub and diatonic_sub.

Returns the reharmonized progression string + per-chord mapping + explanation of each substitution.

Example:

Tritone substitution on a ii-V-I

reharmonize_progression("Dm7-G7-Cmaj7", technique="tritone_sub")

→ "Dm7-Db7-Cmaj7" (G7→Db7, guide tones shared)

Modal interchange on pop progression

reharmonize_progression("C-G-Am-F", technique="modal_interchange")

→ "C-G-Am-Fm" (F→Fm, borrowed from C minor)

Secondary dominants for jazz

reharmonize_progression("C-Am-Dm-G7", technique="secondary_dominant")

→ "C-E7-Am-A7-Dm-G7" (E7 before Am, A7 before Dm)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
intensityNomedium
techniqueNotritone_sub
progressionNoAm-F-C-G
target_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 the full burden. It thoroughly explains the transformation behavior for each technique, the meaning of intensity levels, and explicitly states the return value (progression string + mapping + explanation). This is significantly transparent. However, it does not explicitly state whether the tool modifies project state or is purely computational, which would have made it 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 long but every sentence earns its place. It is front-loaded with a clear summary, then systematically explains each parameter with examples and musical rationale. The use of bullet-like formatting for techniques and intensity levels improves scannability without wasting words.

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's complexity (4 parameters, 5 techniques, multiple intensity levels) and absence of annotations, the description is remarkably complete. It covers input format, all technique variants with musical context, intensity semantics, target_chord behavior, and the return payload. The existence of an output schema means return-value details are not strictly needed in the description.

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%, so the description must fully compensate. It does: every parameter (progression, technique, intensity, target_chord) is explained with concrete musical examples, possible values, and their effects. This goes far beyond the bare schema, providing essential context for correct invocation.

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 opens with a specific verb and resource: 'Reharmonize a chord progression — substitute chords with functionally equivalent alternatives for richer harmony.' This clearly states the tool's function and distinguishes it from sibling tools like create_chord_progression or modulate_progression. The detailed technique list further clarifies its unique scope.

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 clear context for when to use the tool (reharmonization for richer harmony) and details each technique's musical purpose (e.g., 'Jazz standard', 'Adds forward motion'). However, it does not explicitly name alternative tools or state when not to use this tool compared to siblings, so it misses the explicit exclusion guidance for a 5.

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-ai/opendaw-mcp'

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