Skip to main content
Glama

mcp_opendaw_create_motif_development

Transform a short motif into a continuous, evolving melodic line using development stages like sequence, fragment, inversion, and cadence.

Instructions

Develop a motif into a through-composed melodic line that evolves.

Takes a short motif (2-8 notes) and builds a continuous melodic line that develops through compositional stages: statement, sequential repetition (up/down), fragmentation (shorter segments), inversion, octave displacement, and cadence. This is the Beethoven 5th approach — a 4-note seed grows into an entire melodic arc.

Unlike create_variations (separate regions, each a full transformation), create_motif_development writes ONE continuous line that flows through stages without stopping. Unlike create_sequence (pure transposition), this tool mixes multiple development techniques in sequence.

motif: Comma-separated scale degrees (1-7) or MIDI pitches. Scale degrees: 1=root, 2=2nd, 3=3rd, etc. 0=rest. MIDI pitches: 60,62,64,65 etc (when use_midi=true implicit if >7). Example: "1,1,1,2" or "60,60,60,62" scale: Scale type (major, minor, harmonic_minor, dorian, etc.). root: Root note name (C, D#, Bb, etc.). octave: MIDI octave for root (4 = C4=60). steps: Comma-separated development stages: "statement" — play motif as-is "sequence_up" — transpose up by a 4th (5 semitones) "sequence_down" — transpose down by a 4th "fragment" — play first half of motif "fragment_end" — play second half of motif "invert" — invert around root pitch "octave_up" — shift up one octave "octave_down" — shift down one octave "expand" — double note durations "compress" — halve note durations "cadence" — resolve to root (scale degree 1, longer duration) step_duration: Duration of each note in beats (0.25 = 16th). velocity: Base velocity 0-1. unit_index: AU index with a note track. track_index: Note track index within the AU. start_beat: Where the development starts.

Returns total notes, stage count, pitches used.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
rootNoA
motifYes
scaleNominor
stepsNostatement,sequence_up,sequence_down,fragment,invert,sequence_up,fragment,octave_up,cadence
octaveNo
velocityNo
start_beatNo
unit_indexNo
track_indexNo
step_durationNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

With no annotations provided, the description carries full burden. It explains the process (stages, continuous line) and notes that it writes one continuous line. It could mention whether it modifies existing data or creates new, but the description is fairly transparent 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 with a summary, then detailed explanations. It front-loads the purpose and uses bullet points for parameters. While slightly long, every sentence adds value.

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 tool's complexity (10 parameters, generative process) and the presence of an output schema, the description covers input, process, and output (returned metrics) completely. It leaves no major gaps.

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 description coverage is 0%, so the description must compensate. It explains every parameter in detail, including motif formats (scale degrees or MIDI, with examples), step options, and defaults. This is exemplary.

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 verb (develop), resource (motif), and output (through-composed melodic line). It explains the compositional stages and distinguishes from siblings like create_variations and create_sequence, which enhances purpose clarity.

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 provides explicit guidance on when to use this tool (to evolve a short motif into a continuous line) and when not (if separate regions are needed, use create_variations; if pure transposition, use create_sequence). This helps the agent select correctly.

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