Skip to main content
Glama

mcp_opendaw_reharmonize_progression

Replace chords in a progression with harmonically equivalent alternatives using techniques like tritone substitution, secondary dominants, or modal interchange to create richer harmony.

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?

No annotations are provided, so the description carries the full burden. It details the substitution techniques and return values (reharmonized string + mapping + explanation). However, it lacks information on side effects, error handling, or prerequisites (e.g., valid chord format). It is transparent enough for most use cases.

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: a summary sentence, then parameter breakdowns, followed by multiple practical examples. Every sentence adds value, and the examples illustrate usage. It is comprehensive without being verbose.

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 (multiple substitution techniques, parameter interactions), the description is highly complete. It covers concept, each technique, parameter meanings, and provides three realistic examples. The return value is described. It meets the high bar for completeness.

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. It explains each parameter in detail: progression format with examples, all five techniques with musical explanations, intensity levels with percentages, and target_chord indexing. This adds significant meaning 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 the tool's purpose: 'Reharmonize a chord progression — substitute chords with functionally equivalent alternatives for richer harmony.' The verb is distinct ('reharmonize'), the resource is specific ('chord progression'), and it differentiates from sibling tools like 'create_chord_progression' or 'modulate_progression' by focusing on substitution rather than creation or modulation.

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 the tool ('to transform a progression without changing its fundamental direction') and provides context for reharmonization. However, it does not explicitly state when not to use it or compare it to alternatives like 'modulate_progression', leaving some ambiguity for the agent.

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