Skip to main content
Glama

mcp_opendaw_create_chaconne

Compose a chaconne with repeating bass line, chord progression, and developing variations. Define bass notes, rhythms, chords, and choose from baroque, romantic, jazz, minimalist, or contemporary styles.

Instructions

Create a chaconne — repeating bass + chord progression + developing variations.

A chaconne is a set of variations over a repeating bass line and harmonic progression. Unlike ground bass (bass only) or passacaglia (bass + variations), a chaconne explicitly repeats both the bass AND the chord progression, building variations on top of this fixed harmonic framework.

Bass pattern: space-separated note names (e.g. "C2 G2 A2 E2"). Bass rhythm: space-separated durations in beats (e.g. "1 1 1 1"). Chord pattern: comma-separated chord names aligned with bass notes (e.g. "C,Em,Am,G"). Supports major, minor, dim, aug, maj7, m7, 7. Variation styles:

  • baroque: descending stepwise lines with suspensions, ornaments accumulate

  • romantic: wide intervals, expressive phrases, rubato-like timing

  • jazz: syncopated, chromatic passing tones, swing-like rhythm

  • minimalist: repeating cells with gradual phase shift

  • contemporary: dissonant clusters, intervallic leaps, pointillistic

Creates bass on track_index, chord pads on track_index+1, variation on track_index+2.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
repeatsNo
velocityNo
start_beatNo
unit_indexNo
bass_rhythmNo1 1 1 1
track_indexNo
bass_patternNoC2 G2 A2 E2
chord_patternNoC,Em,Am,G
variation_styleNobaroque

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

With no annotations, the description bears full burden for behavioral disclosure. It explains the track layout (bass on track_index, chord pads on track_index+1, variation on track_index+2) and variation styles, which adds value. However, it does not discuss safety, idempotency, error conditions, or implications of repeated calls.

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, starting with a clear definition and purpose, then detailing parameter formats and styles, and ending with track layout. It is appropriately sized with minimal redundancy, though slightly verbose in the variation style descriptions.

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 complexity and the presence of an output schema (per context signals), the description provides sufficient conceptual and behavioral context. It covers the chaconne structure, parameter semantics, and track placement. Minor gaps exist, such as error handling or validity of inputs, but overall it is complete for a creative tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, so the description must compensate. It explains formats for bass_pattern, bass_rhythm, chord_pattern, and variation_style, adding meaning beyond the schema. However, it leaves repeats, velocity, start_beat, unit_index, and track_index unexplained, covering only about 5 of 9 parameters.

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 defines what a chaconne is, specifies it creates a repeating bass line and chord progression with variations, and explicitly distinguishes it from ground bass and passacaglia. This helps the agent understand the tool's unique purpose among siblings.

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 for when to use a chaconne by defining it and contrasting with ground bass and passacaglia. However, it does not explicitly state when not to use this tool or recommend alternatives, though the sibling tools for ground bass and passacaglia exist.

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