Skip to main content
Glama

mcp_opendaw_create_reggae_arrangement

Generate an authentic roots reggae arrangement with one-drop drums, melodic bass, skank guitar, and organ bubble. Control BPM, bars, root, and octave to fit your track.

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
Behavior3/5

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

No annotations are provided, so the description must carry the full burden of behavioral disclosure. It thoroughly describes the musical output (patterns per track, BPM feel, bass role) and states returns ('notes created per track and total'). However, it does not disclose critical side effects: whether existing notes on the specified tracks are overwritten, whether tracks must already exist, or whether the tool creates tracks. 'unit_index: AU index with note tracks' implies an existing unit, but the mutation behavior is unstated.

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-structured with bullet points per track and a clear opening summary. It includes examples and front-loads the primary purpose. However, it is somewhat repetitive: the 'one-drop' concept and 'bass is the lead' are explained multiple times (in the intro, in track descriptions, and in the BPM paragraph). Some trimming could improve conciseness without losing substance.

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 tool with 11 parameters, 0% schema coverage, and no annotations, the description is largely complete: it covers musical style, defaults, parameter meanings, and return behavior. It also references the output schema ('Returns notes created per track and total'). Gaps remain: two parameters undescribed and no mention of prerequisite/destructive behavior. Despite these gaps, the description provides enough context for an agent to decide whether and how to invoke the tool.

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 coverage is 0%, so the description must compensate. It adds meaningful context for 9 of 11 parameters: bpm (65-95 range, 80 = classic roots), bars (4-16), root ('A is a classic reggae key — Am'), octave ('2 = A2=45, standard reggae bass register'), unit_index, and all four track indices. However, it omits 'velocity' and 'start_beat', leaving those two parameters without any additional explanation beyond the schema 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 opens with a specific verb and resource: 'Create a full reggae arrangement — one-drop drums + melodic bass + skank guitar + organ across 4 tracks.' It clearly distinguishes this tool from siblings by explicitly contrasting reggae's one-drop feel with rock and funk, and by stating 'fundamentally different from all 10 other arrangements.' The musical specifics (track 0 = drums, track 1 = bass lead, etc.) remove any ambiguity about the tool's scope.

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 implies clear usage context: use for roots reggae arrangements at 65-95 BPM, with examples of classic keys (A) and tempos (72, 80). It differentiates from other genres by explaining how rock and funk handle kick placement versus reggae's drop on 3. However, it does not explicitly name alternative tools (e.g., create_rock_arrangement) or state when NOT to use this tool, so it falls short of full exclusion guidance.

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