Skip to main content
Glama

mcp_opendaw_create_pop_arrangement

Creates a full pop arrangement with verse-chorus-bridge structure, four tracks (drums, bass, chords, melody), and the I-V-vi-IV chord progression at 120 BPM.

Instructions

Create a full pop arrangement with verse-chorus-bridge song structure across 4 tracks.

Pop music with real song form — fundamentally different from all loop-based arrangements:

  • Track 0: Drums — verse (sparse: kick+hat) → chorus (full: kick+snare+hat+crash) → bridge (build: rising energy) → final chorus (maximum density)

  • Track 1: Bass — verse (root notes, sparse) → chorus (octave jumps, driving) → bridge (walking, building) → final chorus (full energy)

  • Track 2: Chords — I-V-vi-IV progression (the "four chords of pop"), played differently per section: verse (light arpeggios), chorus (full block chords), bridge (sus/resolution)

  • Track 3: Melody — catchy hook that varies per section: verse (sparse, low) → chorus (anthemic, high register) → bridge (tension, chromatic) → final chorus (hook + variation)

At 120 BPM (default), this creates a modern pop feel. The I-V-vi-IV progression is the most used chord sequence in pop music (I=0, V=7, vi=9, IV=5) — different from rock's I-IV-V and jazz's ii-V-I. Song structure (verse-chorus-bridge) is the key difference from all loop-based arrangements.

Sections (16 bars default):

  • Verse 1: bars 1-4 (sparse, intimate)

  • Chorus 1: bars 5-8 (full energy, hook)

  • Verse 2: bars 9-12 (sparse + variation)

  • Chorus 2: bars 13-16 (full energy, hook)

  • Bridge: bars 17-20 (tension, build)

  • Final Chorus: bars 21-24 (maximum, hook + variation)

bpm: Tempo (90-140, default 120 = modern pop). bars: Total length in bars (16-32, default 16 = standard pop song). root: Root note (C is the most common pop key). octave: MIDI octave for bass (2 = C2=36, standard bass register). unit_index: AU index with note tracks. drum_track / bass_track / chord_track / melody_track: Track indices.

Returns notes created per track and total.

Example: create_pop_arrangement(bpm=120, root="C", bars=16) create_pop_arrangement(bpm=128, root="G", bars=24)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bpmNo
barsNo
rootNoC
octaveNo
velocityNo
bass_trackNo
drum_trackNo
start_beatNo
unit_indexNo
chord_trackNo
melody_trackNo

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 the full burden. It details per-track behavior per section (e.g., verse sparse, chorus full), BPM range, bar length, default values, and return type. However, it does not disclose whether it clears existing notes or modifies other project state.

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 long but well-organized with bullet points and section breakdowns. It front-loads the purpose and provides high-density information. Slightly verbose but earns its length with musical theory and examples.

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 of 4-track arrangement with detailed patterns per section, the description is remarkably complete. It covers musical theory (I-V-vi-IV progression), section structure, BPM/bars defaults, and return format. Output schema exists, so return values are already defined.

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 coverage is 0%, but the description explains bpm, bars, root, octave, and track indices inline. However, parameters like velocity, start_beat, and unit_index are not described, and schema already has defaults. Description partially compensates but leaves gaps.

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 it creates a full pop arrangement with verse-chorus-bridge structure across 4 tracks (drums, bass, chords, melody). It distinguishes itself from loop-based arrangements and other genre-specific arrangement tools in the sibling list. The verb 'create' and resource 'pop arrangement' are specific and unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description mentions it is 'fundamentally different from all loop-based arrangements' implying use for pop song form, but it does not explicitly contrast with other arrangement tools (e.g., rock, jazz) or state when to use this vs alternatives. No guidance on prerequisites or when not to use.

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