Skip to main content
Glama

mcp_opendaw_create_arrangement_variation

Create musically varied song sections with per-track transformations: adjust drum density, shift bass octaves, transform melodies, and include or skip tracks to build breakdowns, bridges, and drops.

Instructions

Create a musically varied section — not a repeat, a real variation.

Unlike create_genre_sections (which repeats the same loop at different velocities), this tool applies actual musical transformations to each track independently:

  • Drums: density control (0.3 = sparse, 1.0 = full, 1.5 = busy with ghosts)

  • Bass: octave shift (bass_octave_shift = +1/-1/-2)

  • Melody: inversion, transposition, retrograde, or fragment

  • Track inclusion: skip drums/bass/harmony/melody independently

This lets you build a song where each section has real musical variation, not just energy changes. The drop has full drums, the breakdown has inverted melody + no bass, the bridge has sparse drums + octave-up bass.

genre: Any of the 14 arrangement genres (dnb/house/trap/techno/dubstep/ synthwave/trance/disco/afrobeat/rock/jazz/pop/funk/reggae). section_name: Label for this section (e.g. "verse2", "bridge", "drop2"). bpm: Override tempo (None = genre default). root: Override key (None = genre default). bars: Section length in bars (4-32, default 8). start_beat: Where this section starts in the timeline. velocity: Base velocity 0-1. drum_density: 0.3 = sparse (half notes removed), 1.0 = normal, 1.5 = busy (extra ghost notes between hits). bass_octave_shift: 0 = normal, +1 = octave up, -1 = octave down, -2 = sub. melody_transform: "none", "invert", "transpose:5", "transpose:-7", "reverse", "fragment", "octave_up", "octave_down". include_drums/include_bass/include_harmony/include_melody: Set False to skip that track (e.g. breakdown = no drums, no bass).

Returns notes per track and transformations applied.

Example:

Breakdown section: sparse drums, no bass, inverted melody

create_arrangement_variation("dnb", section_name="breakdown", drum_density=0.3, include_bass=False, melody_transform="invert", velocity=0.6)

Bridge: octave-up bass, retrograde melody

create_arrangement_variation("house", section_name="bridge", bass_octave_shift=1, melody_transform="reverse", start_beat=64, bars=4)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bpmNo
barsNo
rootNo
genreYes
velocityNo
bass_trackNo
drum_trackNo
start_beatNo
unit_indexNo
drum_densityNo
include_bassNo
melody_trackNo
section_nameNovariation
harmony_trackNo
include_drumsNo
include_melodyNo
include_harmonyNo
melody_transformNonone
bass_octave_shiftNo

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 full burden and does well: it details drum density ranges, bass octave shifts, melody transforms, and track inclusion flags. It also states the return value ('notes per track and transformations applied'). However, it does not disclose side effects like whether existing regions are overwritten or new ones created.

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?

Long but well-structured: lead statement, contrast, parameter list, return note, and two examples. Each section earns its place, and the formatting makes it scannable.

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 tool's complexity (19 parameters, no annotations), the description is thorough: covers musical behavior, parameter semantics, and examples. The missing track parameter explanations are a notable gap, but the overall context is sufficient for an agent to use the tool correctly.

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

Parameters4/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 most parameters with values and examples (drum_density, bass_octave_shift, melody_transform, include_*). Yet it omits five parameters (bass_track, drum_track, melody_track, harmony_track, unit_index), leaving them unexplained.

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?

Description opens with a specific verb and resource: 'Create a musically varied section — not a repeat, a real variation.' It explicitly contrasts with create_genre_sections and enumerates track transformations, making the purpose unmistakable and differentiating it from siblings.

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?

Provides an explicit alternative: 'Unlike create_genre_sections (which repeats the same loop at different velocities), this tool applies actual musical transformations.' Concrete scenarios (drop, breakdown, bridge) and two examples illustrate when to use it, effectively guiding the agent.

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