Skip to main content
Glama

mcp_opendaw_create_bariolage

Create a bariolage pattern by alternating a fixed pedal note with moving notes in various scales and subdivisions for Baroque-style string textures.

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

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

With no annotations, the description covers what the tool creates, the parameters, and the return value. It does not fully disclose whether it modifies existing tracks or creates new ones, but the parameter names suggest it operates on existing tracks.

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 with clear headings and a concise first line. However, it includes historical context that may be extraneous for an AI agent, making it slightly longer than necessary.

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 complexity (13 params, no schema descriptions), the description covers all parameters and return info. It lacks explicit context on how the created notes integrate into the project (e.g., whether a new clip is created or notes are added to an existing region).

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?

The description provides detailed explanations for all 13 parameters, including default behavior (e.g., pedal_pitch -1 uses root at octave). This compensates for the 0% schema coverage.

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 first sentence clearly states 'Create a bariolage' and explains the technique. It distinguishes from siblings by explicitly contrasting with arpeggiator and montuno, making the purpose distinct.

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 contrasts with arpeggiator and montuno, giving context for when to use this technique (Baroque string). However, it does not explicitly list alternative tools or provide a decision tree for when not to use it.

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