Skip to main content
Glama

mcp_opendaw_create_rnb_arrangement

Create a full modern R&B arrangement with trap-influenced drums, deep sub bass, extended chords, and vocal-style lead. Produces a dark, atmospheric slow-burn track with half-time beat and minor key harmony.

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

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

With no annotations, the description must disclose side effects and prerequisites, but it does not. It mentions 'Programmable feel — not live, but loose' and return values, yet never clarifies whether writing to the specified tracks overwrites existing content, whether tracks must already exist, or what occurs on invalid track indices. This is a critical transparency gap for a tool that writes notes.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is well-structured with a clear opener, bullet-like track breakdown, and a parameter heading, but it is overly long with artist references and theoretical explanations (e.g., 'i-VI-III-VII... same as synthwave') that carry the message without adding tool-specific operational value. It is informative but not concise.

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?

Despite 11 parameters and no annotations, the description supplies substantial context: track-by-track creation details, parameter ranges, examples, and return type. It lacks precondition/error-handling notes, but the combination of genre spec, parameter semantics, and examples makes it sufficient for an agent to invoke correctly in most scenarios.

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 documents 9 of 11 parameters with useful semantics (bpm range, bars multiple of 4, root note, octave register, track indices) and gives example calls. However, it omits velocity and start_beat, which remain only schema titles. The coverage is strong but not complete, so it earns a mid score.

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 'Create a full modern R&B arrangement' followed by a specific genre recipe (trap-influenced drums, sub bass, extended chords, vocal lead). The name and content clearly distinguish it from sibling genre arrangement tools like create_reggae_arrangement or create_synthwave_arrangement.

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?

Strong usage context is provided via tempo ranges (55-85), artist references (The Weeknd, Frank Ocean), and explicit track-by-track musical specifications. However, it never explicitly states when NOT to use this tool or contrasts it with alternative genre tools, leaving the agent to infer applicability from genre.

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