Skip to main content
Glama

mcp_opendaw_modulate_progression

Transpose chord progressions to a new key while preserving chord types and intervals, enabling key changes like relative major/minor or up a fourth.

Instructions

Transpose a chord progression to a new key.

Modulation is the technique of changing key within a song. This tool takes a progression like "Am-F-C-G" (key of A minor) and transposes every chord to a new key while preserving chord qualities (major/minor/ 7th etc.) and interval relationships.

Common modulations:

  • Up a fourth (C→F): most natural, adds energy for chorus

  • Up a fifth (C→G): bright, triumphant

  • To relative major (Am→C): minor→major mood shift

  • To relative minor (C→Am): major→minor mood shift

  • Down a third (C→A): darker, bridge section

progression: Source progression (e.g. "Am-F-C-G"). target_key: Target key root note (e.g. "C", "F", "D", "Bb"). direction: "up" or "down" (affects octave placement, default "up").

Returns the modulated progression string + per-chord mapping.

Example:

A minor → C major (relative major)

modulate_progression("Am-F-C-G", target_key="C")

→ "C-G-Am-F" (I-V-vi-IV in C major)

A minor → F (up a fourth for chorus)

modulate_progression("Am-F-C-G", target_key="F")

C major → A minor (relative minor for bridge)

modulate_progression("C-G-Am-F", target_key="A")

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
directionNoup
target_keyNoC
progressionNoAm-F-C-G

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 discloses that chord qualities are preserved, direction affects octave placement, and the return value includes a per-chord mapping. This goes beyond a basic definition, though it does not explicitly state side-effect behavior (e.g., whether the project is modified).

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is well-structured with a lead sentence, explanatory paragraph, common modulation list, parameter docs, and examples. It is somewhat lengthy, but each section adds useful information; no wasted sentences.

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 what the tool does, how to invoke it, common use cases, and what it returns. An output schema exists, so detailed return format is not required. It could mention edge cases or errors, but overall it is sufficient for selection and correct invocation.

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?

The input schema has 0% description coverage, but the tool description fully documents all three parameters with examples (progression, target_key, direction) and notes the default for direction. This compensates entirely for the missing schema descriptions.

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+resource: 'Transpose a chord progression to a new key.' It clearly distinguishes this tool from siblings like reharmonize_progression or transpose_notes by emphasizing preservation of chord qualities and interval relationships. The scope is unambiguous.

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 with 'Common modulations' and musical scenarios (chorus, bridge, mood shifts), and example invocations. However, it does not explicitly mention when not to use this tool or name alternative tools, so it lacks explicit 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-ai/opendaw-mcp'

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