Skip to main content
Glama

mcp_opendaw_create_soul_arrangement

Create a complete soul arrangement with gospel drums, melodic bass, Rhodes chords, and horn stabs across four tracks, with adjustable tempo and key for Motown/Stax styles.

Instructions

Create a full soul arrangement — gospel drums + melodic bass + Rhodes chords + horn stabs across 4 tracks.

Motown / Stax / Atlantic soul — Otis Redding, Aretha Franklin, Marvin Gaye style:

  • Track 0: Drums — gospel-influenced: steady kick with ghost notes, backbeat snare, ride cymbal with triplet feel. Soul groove is laid-back but deep — the pocket is behind the beat.

  • Track 1: Bass — melodic walking bass: root → fifth → octave → walk to next chord tone. Not just root pumping — soul bass sings.

  • Track 2: Keys — Rhodes/Wurlitzer chord stabs on I-IV-vi-V gospel changes. Warm, gospel-tinged voicings (maj7, min9). The harmonic foundation — church-meets-R&B.

  • Track 3: Horns — Motown horn section: stabs on chord changes, melodic fills at phrase ends. Tight, arranged, call-and-response with vocals.

At 72 BPM (default), this creates the classic slow soul groove — deep pocket, gospel changes, warm Rhodes. The I-IV-vi-V progression is the gospel quartet influence that separates soul from funk (which vamps on one chord) and from pop (which uses I-V-vi-IV). Soul is about feel and melody, not rhythm complexity.

bpm: Tempo (65-90, default 72 = classic slow soul). bars: Arrangement length (4-16, default 8). Must be multiple of 4 for chord changes. root: Root note (C is a warm soul key). octave: MIDI octave for bass (2 = C2=36, standard soul bass register). unit_index: AU index with note tracks. drum_track / bass_track / keys_track / horns_track: Track indices.

Returns notes created per track and total.

Example: create_soul_arrangement(bpm=72, root="C", bars=8) create_soul_arrangement(bpm=80, root="F", bars=16)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bpmNo
barsNo
rootNoC
octaveNo
velocityNo
bass_trackNo
drum_trackNo
keys_trackNo
start_beatNo
unit_indexNo
horns_trackNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

Without annotations, the description carries full burden. It explains what each track does and the default tempo, but does not disclose side effects like overwriting existing notes, whether tracks must be empty, or error conditions. The return format is briefly mentioned.

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 front-loaded with the purpose, then details tracks, style, parameters, and examples. It is somewhat verbose with educational asides (e.g., comparing soul to funk), but overall well-structured and efficient.

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 11 parameters, 0% schema coverage, and a complex output, the description thoroughly covers musical context, track roles, parameter constraints, and provides examples. It gives enough information for an AI agent to correctly 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%, and the description compensates by explaining most parameters (bpm range, bars multiple of 4, root, octave, track indices) with musical context. However, it omits 'velocity' and 'start_beat', which are in the schema but unexplained.

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 the tool creates a full soul arrangement with specific instruments (gospel drums, melodic bass, Rhodes chords, horn stabs) across 4 tracks. It distinguishes from sibling arrangement tools by explicitly referencing the soul genre and artists like Otis Redding and Aretha Franklin.

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 stylistic context for when to use this tool (slow soul groove at 72 BPM, I-IV-vi-V progression) and compares it to funk and pop to differentiate. However, it does not explicitly state when not to use it or mention alternative tools among 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