Skip to main content
Glama

mcp_opendaw_create_two_hand_piano

Creates a two-hand piano arrangement by combining left-hand accompaniment patterns with right-hand melody or chord tones, producing a coherent piano part from a chord progression.

Instructions

Create a two-hand piano arrangement — left hand accompaniment + right hand melody.

The fundamental piano pattern: left hand plays accompaniment (Alberti bass, arpeggios, block chords, or bass+chord), right hand plays melody or chord tones. Unlike create_chord_progression (block chords only) or create_melody (single line), this combines both hands into one coherent arrangement.

chords: JSON array of chord specs, same format as create_chord_progression. Example: '[["C","maj7"],["A","min7"],["D","min7"],["G","dom7"]]' left_hand: Accompaniment pattern for left hand: "block" — full chord sustained for chord_duration "arpeggio_up" — ascending arpeggio (root-third-fifth-octave) "arpeggio_down" — descending arpeggio "arpeggio_updown" — ascending then descending "alberti" — classic Alberti bass (root-third-fifth-third) "bass_chord" — bass note on beat 1, chord for remaining beats right_hand: Right hand pattern: "chord_tones" — top note of each chord as sustained melody "arpeggio" — arpeggiated chord in right hand (higher octave) "melody" — custom melody from melody_pitches parameter melody_pitches: Comma-separated MIDI pitches for right hand melody (only used when right_hand="melody"). Spans entire progression evenly. bass_octave: MIDI octave for bass notes (2 = C2=36). chord_octave: MIDI octave for left hand chords (3 = C3=48). melody_octave: MIDI octave for right hand (5 = C5=72). chord_duration: Length of each chord in beats (4 = one bar at 4/4). arpeggio_rate: Duration of each arpeggio note in beats (0.5 = eighth notes). unit_index: AU index with a note track. track_index: Note track index within the AU. start_beat: Where the arrangement starts (0 = bar 1). velocity: Base velocity 0-1 (left hand slightly quieter).

Returns notes created, left/right hand voicings, and chord count.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
chordsYes
velocityNo
left_handNoarpeggio_up
right_handNochord_tones
start_beatNo
unit_indexNo
bass_octaveNo
track_indexNo
chord_octaveNo
arpeggio_rateNo
melody_octaveNo
chord_durationNo
melody_pitchesNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

No annotations are provided, so the description carries full burden. It details left/right hand patterns, octave settings, velocity base (left hand slightly quieter), and return values (notes, voicings, chord count). It doesn't mention side effects like prerequisite track existence, but covers most behavioral traits 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 well-structured: summary, sibling differentiation, then parameter details. It is lengthy but every sentence adds value. Some parameter groupings could be tighter, but overall it's effective.

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?

Given the complexity (13 parameters, no annotations, output schema exists), the description covers purpose, parameter details, and return values. It is complete enough for an agent to invoke correctly, explaining how each parameter affects the arrangement.

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?

Schema coverage is 0%, but the description provides thorough explanations for all 13 parameters, including examples (e.g., chords format, left_hand patterns, arpeggio types) and default values. This exceeds what the schema provides.

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 'Create a two-hand piano arrangement — left hand accompaniment + right hand melody.' It distinguishes itself from siblings like create_chord_progression and create_melody by explicitly noting that this tool combines both hands into one coherent arrangement.

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 this tool versus alternatives by contrasting with create_chord_progression (block chords only) and create_melody (single line). It does not explicitly state when not to use it, but the differentiation is sufficient.

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