Skip to main content
Glama

mcp_opendaw_create_ground_bass

Create a repeating bass ostinato with a melody that develops over repetitions. Choose from baroque, modal, minimalist, film tension, or folk styles.

Instructions

Create a ground bass — a repeating ostinato bass line with optional melody.

The ground bass (basso ostinato) is one of the oldest composition techniques: a short bass pattern repeats throughout the piece while melodies above it change and develop. Used in baroque (Purcell's Dido's Lament, Bach's Crucifixus), chaconne/passacaglia tradition, jazz modal vamps, and film scoring (repeating tension ostinati).

Unlike passacaglia (which generates variations above the bass), ground_bass creates the pure repeating bass ostinato + a melody line that develops over the repetitions. The melody changes character per repetition cycle.

melody_styles: "baroque" — Stepwise descending lines over the ground. chromatic passing tones, suspensions on strong beats. Purcell/Bach style. Melody descends gradually across repetitions. "modal" — Modal jazz vamp style. Long sustained notes, sparse placement, emphasis on chord tones. Miles Davis / Kind of Blue aesthetic. Melody floats above the bass. "minimalist" — Steve Reich / Philip Glass style. Phase-shifted melodic fragments, repetitive cells, gradual transformation. Melody uses small intervals and repeating patterns. "film_tension" — Dark film scoring style. Minor 2nd and tritone intervals, dissonant suspensions, gradual crescendo. Melody builds tension across repetitions. "folk" — Strophic folk variation style. Pentatonic-leaning melody, simple rhythmic values, phrase repetition with slight variation. Celtic / English folk tradition.

Args: bass_pattern: Space-separated bass notes (e.g. "A2 E2 C2 G2"). Can use note names (A2, C3) or MIDI numbers (45, 52). bass_rhythm: Space-separated durations in beats for each bass note (e.g. "2 2 2 2" = 4 notes each lasting 2 beats = 8-beat cycle). repeats: Number of bass repetitions (2-32). melody_style: Melody character above the ground. unit_index: AU index. track_index: Note track index (bass goes here, melody on track_index+1). start_beat: Starting beat position. velocity: Base velocity 0-1.

Returns bass notes created, melody notes, cycle info, and style.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
repeatsNo
velocityNo
start_beatNo
unit_indexNo
bass_rhythmNo2 2 2 2
track_indexNo
bass_patternNoA2 A2 E2 E2
melody_styleNobaroque

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 must fully disclose behavior. It explains that the bass pattern repeats and the melody develops per cycle, and details melody_styles. However, it omits side effects (e.g., overwriting existing notes), error conditions, or required track state. For a creative tool, this is adequate but not comprehensive.

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

Conciseness3/5

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

The description is well-structured but somewhat verbose, especially the historical background and detailed melody_style descriptions. While informative, it could be more concise for an AI agent. However, it front-loads the purpose and uses clear sectioning.

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, the description covers the main aspects: what it creates, how to use parameters, and what is returned. It does not discuss edge cases or error handling, but it provides sufficient context for typical use.

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?

Schema description coverage is 0%, so the description compensates well. It explains each parameter in the 'Args:' section, including format for bass_pattern and bass_rhythm, range for repeats, and details for melody_style. It adds meaning beyond the schema titles and defaults, though some parameters like unit_index and track_index are only briefly mentioned.

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: 'Create a ground bass — a repeating ostinato bass line with optional melody.' It specifies the verb-action (create), the resource (ground bass), and distinguishes it from passacaglia by explaining the difference. This allows an agent to understand what the tool does and how it differs from siblings like create_passacaglia.

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 explains when to use a ground bass, provides historical context, and contrasts with passacaglia. It also lists melody_styles with detailed descriptions, guiding the agent's choice. However, it does not explicitly state when not to use this tool or provide alternatives for similar tools like create_ostinato.

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