Skip to main content
Glama

mcp_opendaw_create_rock_arrangement

Create a full rock arrangement with drums, bass, guitar power chords, and keys, based on I-IV-V blues harmony and a driving rock beat.

Instructions

Create a full rock arrangement — rock beat drums + bass + power chords + riff across 4 tracks.

Classic rock with blues-based harmony and guitar-driven energy:

  • Track 0: Drums — rock beat: kick on 1 & 3, snare on 2 & 4, with crash on downbeats and fills at bar transitions. The backbone.

  • Track 1: Bass — root-fifth bassline locking with kick drum, with walks between chord changes. Blues-based, driving.

  • Track 2: Guitar — power chords (root+fifth) on chord changes, with palm-muted downstrokes between. The defining instrument.

  • Track 3: Keys — sustained chord pads backing the guitar, filling the midrange. Optional but adds depth.

At 120 BPM (default), this creates a mid-tempo rock feel. The I-IV-V blues-based harmony (A-E-D for key of A, or E-A-D for key of E) is the foundation of rock from Beatles to AC/DC. Power chords are the signature — root+fifth voicings, no third (ambiguous major/minor).

bpm: Tempo (90-160, default 120 = mid-tempo rock). bars: Arrangement length (4-16, default 8). root: Root note (E is the most common rock guitar key — open strings). octave: MIDI octave for bass (2 = E2=40, standard bass register). unit_index: AU index with note tracks. drum_track / bass_track / guitar_track / keys_track: Track indices.

Returns notes created per track and total.

Example: create_rock_arrangement(bpm=120, root="E", bars=8) create_rock_arrangement(bpm=140, root="A", bars=16)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bpmNo
barsNo
rootNoE
octaveNo
velocityNo
bass_trackNo
drum_trackNo
keys_trackNo
start_beatNo
unit_indexNo
guitar_trackNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/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 explains the notes created per track, defaults, and musical details, but lacks clarity on side effects like whether tracks are appended or replaced, or if new tracks are created. This leaves some behavioral ambiguity.

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, track breakdown, parameter list, and examples. It is informative but slightly verbose for the amount of detail, earning a 4.

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 complexity of creating a multi-track arrangement, the description covers track roles, defaults, and examples. However, it omits details on track existence requirements, error handling, and exact return structure beyond 'notes created per track and total'.

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%, and the description fully compensates by explaining each parameter's purpose, allowed ranges, defaults, and musical context (e.g., bpm range 90-160, root note suggestions). Examples further clarify usage.

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 rock arrangement with specific instruments (drums, bass, guitar, keys) and distinguishes from sibling tools like create_blues_arrangement by explicitly mentioning rock genre and musical style.

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 the tool (creating a rock arrangement) with BPM and root note suggestions, and examples. However, it does not explicitly say when not to use it or compare to alternatives.

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