Skip to main content
Glama

mcp_opendaw_create_rnb_arrangement

Generate a contemporary R&B arrangement with trap-influenced drums, deep sub bass, dark extended chords, and vocal-style leads for atmospheric tracks.

Instructions

Create a full modern R&B arrangement — trap-influenced drums + deep sub bass + extended chords + vocal-style lead.

Contemporary R&B (The Weeknd / Frank Ocean / SZA / Brent Faiyaz) — dark, atmospheric, slow-burn:

  • Track 0: Drums — half-time R&B groove: kick on 1 with syncopated ghost, snare/clap on 3, triplet hi-hat rolls. Programmable feel — not live, but loose. Half-time at 68 BPM feels like 34 BPM.

  • Track 1: Bass — deep sub bass: long sustained root notes, occasional octave/fifth movement. More sustain than soul, less movement than funk. The low-end foundation — felt more than heard.

  • Track 2: Chords — dark extended voicings (min9, maj7, dom9, min7b5) on i-VI-III-VII minor-key progression. Rhodes/synth pad texture with long sustains. The Weeknd's signature dark harmony — minor key with lush 9ths.

  • Track 3: Lead — vocal-style melodic phrases: wide interval leaps, pentatonic minor with blue notes, long sustained notes with melismatic fills. Call-and-response phrasing — the "sung" quality without actual vocals.

At 68 BPM (default), this creates the contemporary R&B pocket — slow, atmospheric, dark. The i-VI-III-VII progression (same as synthwave but with extended chords and half the tempo) is the modern R&B harmonic language. Half-time drums + sub bass + dark 9ths = The Weeknd "After Hours" aesthetic.

bpm: Tempo (55-85, default 68 = modern R&B sweet spot). bars: Arrangement length (4-16, default 8). Must be multiple of 4. root: Root note (C minor = dark R&B key, common for The Weeknd). octave: MIDI octave for bass (2 = C2=36, sub bass register). unit_index: AU index with note tracks. drum_track / bass_track / chord_track / lead_track: Track indices.

Returns notes created per track and total.

Example: create_rnb_arrangement(bpm=68, root="C", bars=8) create_rnb_arrangement(bpm=75, root="Ab", bars=16)

Input Schema

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

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

No annotations were provided, so the description carries full responsibility. It thoroughly explains behavioral traits: each track's content (drums, bass, chords, lead), musical theory (i-VI-III-VII progression, half-time feel), and return value ('notes created per track and total'). There is no contradiction with annotations as none exist.

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 clear purpose sentence, track-by-track breakdown, parameter explanations, and examples. However, it is slightly verbose (e.g., repeating the tempo feel) and could be streamlined without losing clarity. Still, it earns a high score for effective organization.

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 tool's complexity (genre-specific arrangement with 11 parameters) and the presence of an output schema (indicating return structure), the description covers all necessary aspects: track content, musical theory, parameter guidance, and examples. It is fully sufficient for an agent to use correctly.

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%, but the description adds significant meaning: it explains the purpose of each parameter (e.g., 'bpm: Tempo (55-85, default 68 = modern R&B sweet spot)'), provides examples, and links parameters to musical context (e.g., 'root: Root note (C minor = dark R&B key)'). This far exceeds the bare schema.

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 modern R&B arrangement' with specific verbs ('Create') and resources ('arrangement'). It distinguishes from sibling tools by detailing the R&B style, including artists (The Weeknd, Frank Ocean) and harmonic/melodic characteristics, making it unambiguous.

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: BPM range (55-85, default 68), bar length must be multiple of 4, and example calls. It implicitly suggests use for R&B composition but does not explicitly exclude other genres or state when not to use. Alternatives (sibling tools) are not mentioned but the genre-specific content guides appropriate 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