Skip to main content
Glama

mcp_opendaw_create_reggae_arrangement

Generate a complete roots reggae arrangement with one-drop drums, melodic bass, skank guitar, and organ across four tracks at your chosen tempo and key.

Instructions

Create a full reggae arrangement — one-drop drums + melodic bass + skank guitar + organ across 4 tracks.

Roots reggae with the signature one-drop feel — fundamentally different from all other arrangements:

  • Track 0: Drums — one-drop pattern: kick AND snare TOGETHER on beat 3 (the "drop"), with hi-hat on all 8ths. No kick on beat 1 — the emptiness on 1 is the reggae feel. Organ bubble on 8th off-beats.

  • Track 1: Bass — THE lead instrument in reggae: melodic, repetitive, driving. Root-based with octave and fifth walks, full bar sustain. In reggae, bass carries the melody — not the guitar.

  • Track 2: Guitar — skank: staccato chops on the off-beats (the "and" of 1, the "and" of 2, etc.). The signature reggae guitar sound — short, percussive, on every off-beat. This is the rhythmic backbone, not the drums.

  • Track 3: Keys — organ bubble: Hammond-style sustained chords with a shuffle feel, filling the space between guitar skanks. Adds harmonic richness and the classic roots sound.

At 80 BPM (default), this creates the classic roots reggae pocket — slow, heavy, meditative. The one-drop (kick+snare together on 3) is the fundamental difference from all 10 other arrangements: rock puts kick on 1 & 3, funk puts kick on 1 with syncopation, reggae drops everything on 3 and leaves 1 empty. The bass is the lead instrument — unique among all genres.

bpm: Tempo (65-95, default 80 = classic roots reggae). bars: Arrangement length (4-16, default 8). root: Root note (A is a classic reggae key — Am). octave: MIDI octave for bass (2 = A2=45, standard reggae 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_reggae_arrangement(bpm=80, root="A", bars=8) create_reggae_arrangement(bpm=72, root="D", bars=16)

Input Schema

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

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

Despite no annotations, the description discloses the tool creates notes across 4 tracks with specific patterns, default tempo, parameter ranges, and return value. It lacks explicit mention of side effects (e.g., overwriting existing tracks) but is substantially transparent.

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 structured with intro, track breakdown, context, parameter list, and examples. It is informative but slightly repetitive on one-drop explanation. Length is justified by genre complexity.

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 presence of an output schema and the tool's clear role among many arrangement siblings, the description covers purpose, parameters, behavior, and examples. It omits error handling and prerequisites but is otherwise thorough.

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?

The description explains 7 of 11 parameters (bpm, bars, root, octave, track indices) while velocity, start_beat, unit_index remain undocumented. With 0% schema coverage, it compensates partially but not fully, as some parameters lack meaning beyond defaults.

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 reggae arrangement with specific track roles (one-drop drums, melodic bass, skank guitar, organ) and explicitly contrasts with other arrangements (rock, funk), distinguishing it from sibling tools like mcp_opendaw_create_funk_arrangement.

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 details when to use the tool: for roots reggae arrangements with one-drop feel. It provides explicit guidance on genre-specific differences and includes example calls (create_reggae_arrangement(bpm=80, root='A', bars=8)), effectively guiding selection among many arrangement siblings.

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