Skip to main content
Glama

mcp_opendaw_create_ground_bass

Create a repeating bass ostinato with a developing melody line. Choose from baroque, modal, minimalist, film tension, or folk styles to generate a ground bass pattern for your track.

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
Behavior4/5

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

With no annotations, the description carries the full burden. It discloses that the tool generates both bass and melody, placing melody on track_index+1, and that melody evolves across repetitions per style. It does not explicitly state whether existing notes are overwritten or appended, which is a minor gap for a creation 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?

The description is long but effectively structured: a headline purpose, historical context, a comparative note, styled bullets, and an args list. It's front-loaded with the definition, and each paragraph earns its place, though the historical section could be trimmed without losing critical information.

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?

The tool has 8 parameters, 5 style options, and an output schema; the description covers every parameter with semantics, explains the return value ('Returns bass notes created, melody notes, cycle info, and style'), and clarifies the two-track behavior. The only missing piece is edge-case handling for track_index+1, but overall the description is comprehensive.

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?

All 8 parameters are described with examples and format details beyond schema defaults. For instance, bass_pattern supports note names or MIDI numbers, bass_rhythm includes an example cycle calculation, repeats has a range, and melody_style offers five detailed style descriptions. Since schema_description_coverage is 0%, this fully compensates.

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 opening sentence defines the tool with a specific verb and resource: 'Create a ground bass — a repeating ostinato bass line with optional melody.' It also distinguishes itself from a sibling: 'Unlike passacaglia (which generates variations above the bass), ground_bass creates the pure repeating bass ostinato + a melody line that develops over the repetitions.' This gives clear purpose and differentiation.

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 context for when to use the tool historically ('Used in baroque... jazz modal vamps... film scoring') and explicitly contrasts with passacaglia, implying a choice between the two based on whether you want variations above the bass. However, it does not mention other similar siblings like create_ostinato or create_bassline, so exclusion is limited.

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-ai/opendaw-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server