Skip to main content
Glama

mcp_opendaw_add_chord_tension

Add tension notes like 9th, 11th, or 13th to existing chords for jazz harmony. Extend triads into complex chords without manual pitch calculation.

Instructions

Add a tension/extension note to an existing chord — jazz harmony.

Adds an extension note (9th, 11th, 13th, or alterations) to a chord already on the timeline. This is how triads become jazz chords — stack a 9th on a C major triad and it becomes Cmaj9, add a b13 to a G7 and it becomes G7b13. The extension is calculated from the chord root, so you don't need to know the exact pitch.

extension: The tension note to add:

  • "9" — major 9th (2 semitones above root, +14 from root). Adds color and warmth. C → D. The most common jazz extension.

  • "b9" — minor 9th (1 semitone above root, +13). Dark, tense. Dominant chords in minor keys, flamenco, film scores. C → Db.

  • "#9" — augmented 9th (3 semitones, +15). The Hendrix chord sound. Bluesy, gritty. C → D#.

  • "11" — perfect 11th (5 semitones above root, +17). Suspended, open. C → F. Can clash with 3rd — use carefully.

  • "#11" — augmented 11th (6 semitones, +18). Lydian sound. Dreamy, floating. C → F#. Common in modal jazz.

  • "13" — major 13th (9 semitones above root, +21). Full, rich. The ultimate jazz extension. C → A. Adds completeness.

  • "b13" — minor 13th (8 semitones, +20). Dark, dramatic. Minor key dominants. C → Ab. Spanish/orchestral feel.

chord_position: Beat position of the chord (finds root = lowest note). octave: Which octave to place the extension in (3-7, default 5). Higher = more color, lower = more grounded. velocity: Velocity of the added note (0-1, default 0.6 = subtle).

Returns root pitch, extension pitch, extension name, chord size.

Example:

Add 9th to first chord — Cmaj → Cmaj9

add_chord_tension(0, 2, 0, 0.0, extension="9")

Add b13 for dark dominant — G7 → G7b13

add_chord_tension(0, 2, 0, 4.0, extension="b13")

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
octaveNo
velocityNo
extensionNo9
unit_indexYes
track_indexYes
region_indexYes
chord_positionYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

No annotations are provided, so the description carries full burden. It explains that extensions are calculated from the chord root and returns pitch info, but lacks details on side effects, reversibility, or error handling. It adds context like potential clashes (11th with 3rd), which is helpful but not exhaustive.

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: one-line summary, conceptual explanation, detailed extension list with musical character, other parameters, return values, and examples. Every section adds value, though the extension list could be slightly condensed without losing information.

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?

Given the tool's musical complexity and 7 parameters, the description covers purpose, parameter roles, and return values. It includes practical examples and educational content. However, it does not address edge cases like invalid chord_position or missing chord, which would improve completeness.

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 description coverage, the description explains the most important parameters (extension, chord_position, octave, velocity) in detail with musical context. The index parameters are self-explanatory. 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 it adds tension/extension notes to chords in a jazz harmony context. It uses specific verbs and resources, and the purpose is distinct from sibling tools like add_chord_progression or invert_chord_notes.

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 extensive guidance on when to use each extension type (e.g., 'most common jazz extension', 'dark, tense'), and gives examples for Cmaj9 and G7b13. However, it does not explicitly contrast with alternative tools or state when not to use it.

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