Skip to main content
Glama

mcp_opendaw_create_progression_from_key

Generates a diatonic chord progression from a detected key and mode, eliminating manual chord entry. Choose style for genre-appropriate chords.

Instructions

Auto-generate a diatonic chord progression from a detected key — no manual chord typing.

Takes key + mode (from detect_key output) and generates a genre-appropriate diatonic progression using scale degrees. Eliminates the need to manually write [["Am","min"],["F","maj"]...] — just pass key="A", mode="minor".

key: Root note name (C, C#, D, D#, E, F, F#, G, G#, A, A#, B). mode: "major" or "minor" (natural minor scale). style: Progression style:

  • "pop" — I-V-vi-IV (major) / i-VI-III-VII (minor) — "four chords of pop"

  • "jazz" — ii-V-I (major) / ii-V-i (minor) — jazz turnaround

  • "rock" — I-IV-V (major) / i-iv-V (minor) — blues/rock

  • "synthwave" — i-VI-III-VII (minor) — synthwave/emotional

  • "folk" — I-IV-vi-V (major) / i-iv-VII-III (minor) — folk/americana

  • "lofi" — ii-V-i (minor) or I-vi-IV-V (major) — lofi/jazzy unit_index: AU index with a note track. track_index: Note track index within the AU. start_beat: Where the progression starts (0 = bar 1). chord_duration: Length of each chord in beats (4 = one bar at 4/4).

Returns: notes_created, chords, voicings, progression (chord names), key, mode.

Pipeline: detect_key("track.wav") → {key: "A", mode: "minor"} → create_progression_from_key("A", "minor", "synthwave") → create_harmonic_arrangement("Am-F-C-G")

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
keyYes
modeNomajor
styleNopop
start_beatNo
unit_indexNo
track_indexNo
chord_durationNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

With no annotations provided, the description takes on full transparency duty. It describes the generated output (notes_created, chords, voicings, etc.) and explains the genre-appropriate nature of the progression. However, it does not mention potential side effects (e.g., overwriting existing notes) or dependencies beyond detect_key, leaving some transparency gaps.

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 clear opening, bullet-style parameter explanations, and a pipeline example. It is front-loaded with the core purpose and remains informative without redundancy.

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?

For a tool with 7 parameters and no annotations, the description provides comprehensive context: usage flow (detect_key → this tool → create_harmonic_arrangement), all parameter details, and return fields. It integrates well with sibling tools and covers the expected pipeline.

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 description explains every parameter in detail, including key, mode, style with examples, and positional parameters (unit_index, track_index, etc.). Since schema description coverage is 0%, the description fully compensates and adds meaning beyond the schema titles.

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: auto-generate a diatonic chord progression from a detected key. It uses specific verbs ('auto-generate') and distinguishes from manual methods ('no manual chord typing'), effectively differentiating from sibling tools like create_chord_progression.

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 usage context: it should be used after detect_key and eliminates manual chord typing. It implies when to use this tool over manual alternatives, but does not explicitly list conditions when not to use it or mention other alternative tools.

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