Skip to main content
Glama

mcp_opendaw_create_passacaglia

Create a passacaglia by defining a repeating bass ostinato and evolving chord harmonies above it, with control over rhythm, variation style, and arrangement parameters.

Instructions

Create a passacaglia — repeating bass ostinato with evolving harmonies above.

A foundational Baroque form (Bach BWV 582, Buxtehude) adapted to modern contexts (film scoring, metal, electronic). A short bass pattern (4-8 notes) repeats throughout while chords or arpeggiations evolve above it, creating cumulative tension. Distinct from ostinato (single repeating pattern), pedal_point (single sustained note), and bordun (drone chord).

bass_pattern: Space-separated MIDI pitches for the bass ostinato (e.g. "36 43 41 36" = C2 G2 F2 C2). Default is a classic descending bass. bass_rhythm: Space-separated durations in beats matching bass_pattern (e.g. "1 1 1 1" = quarter notes, "0.5 0.5 1 2" = syncopated). bass_repeats: How many times the bass pattern repeats (1-16, default 4). chord_pattern: Comma-separated chord names for the upper voices (e.g. "Cm,Ab,Eb,Bb"). Supports: maj, min, m7, maj7, dom7, sus2, sus4, dim, aug. If fewer chords than repeats, chords cycle. chord_octave: Octave for chord notes (1-8, default 4). variation_style: How upper harmonies are voiced — "block" (sustained chords), "arpeggiated" (broken chord pattern), "melodic" (stepwise counter-melody). beats_per_bar: Time signature beats (3/4=3, 4/4=4, 6/8=6, default 4). bass_velocity: Velocity of bass notes (0-1, default 0.75). chord_velocity: Velocity of chord/variation notes (0-1, default 0.55). unit_index: AU index with note track (-1 = find first AU with note tracks). track_index: Note track index within the AU. start_beat: Position in beats where the passacaglia begins.

Returns notes created, bass pattern length, total bars, variation style.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
start_beatNo
unit_indexNo
bass_rhythmNo1 1 1 1
track_indexNo
bass_patternNo36 43 41 36
bass_repeatsNo
chord_octaveNo
bass_velocityNo
beats_per_barNo
chord_patternNoCm,Ab,Eb,Bb
chord_velocityNo
variation_styleNoblock

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

Describes the internal behavior (repeating bass pattern, evolving harmonies, variation styles) and output (returns notes created, etc.). Lacks details on error handling or invalid input, but is thorough for a creative tool.

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?

Well-structured with upfront purpose, historical context, differentiation, and detailed parameter list. A bit verbose but well-organized and front-loaded.

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?

Covers musical form, parameter details, return values, and usage context. No annotations exist, but the description fully compensates. Suitable for a 12-parameter tool with no required inputs.

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?

Provides extensive parameter descriptions with examples, defaults, and supported values (e.g., MIDI pitches, chord types, velocity ranges). Adds significant meaning beyond the schema titles and defaults.

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?

Clearly states the tool creates a passacaglia with a specific verb+resource structure. Differentiates from related forms like ostinato and pedal_point, providing historical and modern context.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly distinguishes this tool from siblings (ostinato, pedal_point, bordun) with a direct comparison. Describes the musical context and appropriate usage scenarios.

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