Skip to main content
Glama

mcp_opendaw_create_afrobeat_arrangement

Create a full afrobeat arrangement with polyrhythmic drums, bass, horns, and guitar tracks, inspired by Fela Kuti. Specify BPM, root note, and bars to generate a 4-track polyrhythmic interlock.

Instructions

Create a full afrobeat arrangement — polyrhythmic drums + bass + horns + guitar across 4 tracks.

Fela Kuti-style afrobeat with all elements locked in polyrhythmic interlock:

  • Track 0: Drums — layered polyrhythm: kick pattern, shaker pattern, clave-like accents. The foundation is 12/8 feel in 4/4 time — triplets over straight beats, the African polyrhythmic heartbeat.

  • Track 1: Bass — repetitive ostinato bassline, rooted in the key, driving and hypnotic. Afrobeat bass doesn't rest — it's the engine alongside the drums, locking with the kick.

  • Track 2: Horns — brass section stabs and sustained chords. Call-and-response between horn hits and space. Minor key, soulful.

  • Track 3: Guitar — rhythmic chord stabs on the off-beats, the "chanka" pattern that defines the groove. Two-note voicings, percussive and tight.

At 120 BPM (default), this creates the classic afrobeat feel — not too fast, not too slow, with room for polyrhythmic layering. The 4-track arrangement (first non-electronic genre) is the key difference: horns and guitar add organic texture that electronic arrangements don't have.

bpm: Tempo (100-130, default 120 = classic afrobeat). bars: Arrangement length (8-32, default 8). Afrobeat needs long forms. root: Root note (F is the classic afrobeat key — Fela's preference). octave: MIDI octave for bass (2 = C2=36, audible low end). unit_index: AU index with note tracks. drum_track / bass_track / horn_track / guitar_track: Track indices.

Returns notes created per track and total.

Example: create_afrobeat_arrangement(bpm=120, root="F", bars=8) create_afrobeat_arrangement(bpm=110, root="Ab", bars=16)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bpmNo
barsNo
rootNoF
octaveNo
velocityNo
bass_trackNo
drum_trackNo
horn_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 provided, so description bears full burden. It details the polyrhythmic interlock and track roles, but does not disclose whether existing notes on those tracks are overwritten, or if track creation is handled. Some behavioral aspects are implicit.

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?

The description is well-structured: starts with purpose, then details each track, followed by parameter explanations and examples. Every sentence adds value, and the length is appropriate for the 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 11 parameters, no annotations, and output schema existence, the description covers musical intent, track roles, parameter defaults, and example calls. It lacks details on handling missing tracks or the velocity/start_beat parameters, but is largely complete for the genre-specific arrangement.

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 description compensates. It explains 9 of 11 parameters with musical context, defaults, and examples. However, 'velocity' and 'start_beat' are not mentioned in the parameter descriptions, leaving 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 'Create a full afrobeat arrangement' with specific verb and resource, and distinguishes it from sibling tools like create_acid_arrangement or create_ambient_arrangement by specifying the genre and track layout.

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 explains when to use this tool for Fela Kuti-style afrobeat and contrasts with electronic arrangements. It provides defaults and example use cases, but does not explicitly state when not to use it or mention alternative tools for other genres.

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