Skip to main content
Glama

mcp_opendaw_create_song_with_variations

Create a complete song with real musical variations between sections in one call. Use presets for drums, bass, melody, and track exclusion to shape each section.

Instructions

Build a complete song with real musical variations between sections — one call.

Unlike create_genre_sections (which repeats the same loop at different velocities), this creates a song where each section has actual musical variation: drum density changes, bass octave shifts, melody transforms, and track exclusion. All 14 genres supported.

sections: Comma-separated section specs. Each spec is: name:bars:velocity:preset

  • name: Section label (e.g. "verse1", "chorus", "bridge")

  • bars: Length in bars (4-32)

  • velocity: Base velocity 0-1

  • preset: One of:

    • "full" — all tracks, normal density

    • "drums_only" — drums only, others silenced

    • "drums_bass" — drums + bass, no harmony/melody

    • "full_busy" — all tracks, busy drums (density 1.5)

    • "breakdown" — sparse drums (0.3), no bass, inverted melody

    • "melody_transpose5" — full, melody transposed +5 semitones

    • "melody_transposeN" — full, melody transposed N semitones

    • "melody_invert" — full, melody inverted around middle C

    • "melody_reverse" — full, melody retrograde

    • "melody_octave_up" — full, melody up one octave

    • "bass_octave_up" — full, bass up one octave

    • "bass_sub" — full, bass down two octaves (sub bass)

    • "fade" — drums + bass, sparse, low velocity (outro)

    • "drop" — all tracks, busy drums, octave-up bass (climax)

Default: "intro:4:0.5:drums_only,verse1:8:0.8:full,chorus:8:1.0:full_busy, verse2:8:0.8:melody_transpose5,bridge:4:0.6:breakdown,outro:4:0.4:fade" = 36-bar song with 6 varied sections.

apply_mix: If True, calls apply_genre_mix after all sections. apply_humanize: If True, calls apply_genre_humanization after mix. apply_master: If True, calls add_mastering_chain after humanize.

Returns sections created, transforms per section, total notes, and pipeline status.

Example:

36-bar DnB song with 6 varied sections

create_song_with_variations("dnb")

48-bar house epic with custom sections

create_song_with_variations("house", sections="intro:8:0.4:drums_only,build:8:0.7:drums_bass,drop:8:1.0:drop, breakdown:8:0.5:breakdown,drop2:8:1.0:full_busy,outro:8:0.3:fade")

24-bar minimal techno

create_song_with_variations("techno", sections="intro:4:0.5:drums_only,main:8:0.8:full,drop:4:1.0:full_busy,outro:8:0.4:fade", apply_mix=True, apply_humanize=True, apply_master=True)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bpmNo
rootNo
genreYes
sectionsNointro:4:0.5:drums_only,verse1:8:0.8:full,chorus:8:1.0:full_busy,verse2:8:0.8:melody_transpose5,bridge:4:0.6:breakdown,outro:4:0.4:fade
apply_mixNo
bass_trackNo
drum_trackNo
unit_indexNo
apply_masterNo
melody_trackNo
harmony_trackNo
apply_humanizeNo

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 disclosure burden. It details what happens inside the tool: section variations, track exclusion, and that booleans trigger downstream calls (apply_genre_mix, apply_genre_humanization, add_mastering_chain). It does not explicitly state necessary project state or destructive behavior, but for a generative creation tool the stated behavior is largely sufficient.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is long but well-structured: purpose, differentiation, parameter format, default value, downstream flags, return value, and examples. The preset list earns its place because it is essential for correctly constructing the sections parameter. Information is front-loaded with the core purpose and alternative distinction.

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?

For a complex 12-parameter tool with no annotations, the description covers the central workflow, defaults, and expected returns. The presence of an output schema reduces the need to elaborate the return structure. Gaps remain for genre-specific required parameters and track/unit selections, but examples and detailed sections documentation make the tool usable for primary cases.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/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 thoroughly documents 'sections', including the spec format and all 14 presets, plus apply_mix/humanize/master. However, bpm, root, bass_track, drum_track, unit_index, melody_track, and harmony_track are left unexplained, leaving significant parameter semantics unresolved.

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 a specific verb+resource: 'Build a complete song with real musical variations between sections — one call.' It clearly distinguishes from sibling create_genre_sections by contrast ('Unlike create_genre_sections...') and states all 14 genres supported.

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?

Explicit guidance is provided: it tells when to use this tool over create_genre_sections, explains the sections format with preset options, includes defaults, and shows three practical examples for different genres. Pipeline order for apply_mix, apply_humanize, and apply_master is also specified.

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