Skip to main content
Glama

mcp_opendaw_create_bariolage

Generate a bariolage pattern by alternating a fixed pedal note with moving scale or arpeggio notes. Create two-voice textures in openDAW with configurable pattern, subdivision, and velocities.

Instructions

Create a bariolage — rapid alternation between a fixed pedal pitch and moving notes.

Bariolage is a Baroque string technique (Bach, Vivaldi, Handel) where a fixed note (typically an open string) rapidly alternates with moving notes that ascend, descend, or follow a melodic pattern. This creates a layered, cross-register texture — two streams of sound perceived simultaneously.

Unlike arpeggiator (cycles chord tones) or montuno (syncopated chord stabs), bariolage creates a two-voice illusion from a single voice: the pedal pitch acts as a drone/anchor while the moving notes create melodic interest above or below it.

Moving patterns: scale_asc — ascending scale notes scale_desc — descending scale notes scale_wave — alternating ascending/descending arpeggio — chord tones rotating chromatic — chromatic approach notes

Subdivisions: 8th, 16th, 32nd — determines speed of alternation

Args: root: Root note name (C, C#, D, ...). scale: Scale name (major, minor, dorian, mixolydian, harmonic_minor). bars: Number of bars (1-8). octave: Starting MIDI octave (2-6). pedal_pitch: MIDI pitch for the fixed pedal note. If -1, uses root at the specified octave (e.g., G4 = 67). moving_pattern: Pattern for moving notes (scale_asc, scale_desc, scale_wave, arpeggio, chromatic). subdivision: Note subdivision (8th, 16th, 32nd). velocity: Base velocity for moving notes 0-1. pedal_velocity: Velocity for pedal notes 0-1 (usually louder). accent_pedal: If True, pedal notes get accent (slightly louder). unit_index: AU index. track_index: Note track index. start_beat: Starting beat position.

Returns notes created, pedal/moving note counts, and pattern info.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
barsNo
rootNoG
scaleNomajor
octaveNo
velocityNo
start_beatNo
unit_indexNo
pedal_pitchNo
subdivisionNo16th
track_indexNo
accent_pedalNo
moving_patternNoscale_asc
pedal_velocityNo

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 carry the full behavioral burden. It discloses some behaviors (like pedal_pitch defaulting to root when -1, accent_pedal adding accent, and return values), but it does not state whether notes are added or appended, whether existing notes are overwritten, or any prerequisites like valid track/unit indices. This leaves the mutation semantics unclear.

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 lengthy but well-structured: definition, historical context, contrast with alternatives, pattern/subdivision lists, args, and return value. It is front-loaded with the core definition and all content serves a purpose, though some historical background could be trimmed for an agent-focused description.

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?

For a 13-parameter tool with no schema descriptions and no annotations, this description is remarkably complete: it explains the musical concept, all parameters, pattern options, subdivisions, and return value. It also names alternatives, making it easy for an agent to decide when to use this tool.

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?

With 0% schema description coverage, the description fully compensates by listing all 13 parameters with meaningful explanations, including value ranges (bars 1-8, octave 2-6, velocity 0-1), pattern enums, and the special -1 behavior for pedal_pitch. This is the primary source of parameter understanding.

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 opens with 'Create a bariolage — rapid alternation between a fixed pedal pitch and moving notes,' which clearly states the verb, resource, and core behavior. It also explicitly distinguishes bariolage from arpeggiator and montuno, making it easy to differentiate from sibling tools.

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?

The description explicitly contrasts bariolage with arpeggiator and montuno, explaining that arpeggiator cycles chord tones and montuno does syncopated chord stabs, while bariolage creates a two-voice illusion. This gives the agent clear when-to-use vs. when-not-to-use guidance.

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