Skip to main content
Glama

mcp_opendaw_create_gospel_arrangement

Create a gospel arrangement featuring shuffle drums, walking bass, Hammond organ stabs, and SATB choir call-and-response in a slow groove.

Instructions

Create a full gospel arrangement — shuffle drums + walking bass + Hammond organ + choir.

Gospel music — the foundation of soul, R&B, and modern pop:

  • Track 0: Drums — gospel shuffle. Kick on 1, snare on 2+4 with ghost notes, hi-hats with triplet shuffle feel. The "pocket" is deep — slightly behind the beat. Dynamics are expressive.

  • Track 1: Bass — walking bass line through I-IV-V-I progression. Root → 3rd → 5th → approach note. Warm, supportive.

  • Track 2: Hammond B3 organ — chord stabs with Leslie rotation feel. Triadic voicings, 2nd inversion common. The Hammond is the signature sound of gospel — drawbar harmonics.

  • Track 3: Choir — sustained SATB voicings. Call-and-response with organ. Long notes, rich harmony, the "church" sound.

Ab major default — flat keys are traditional for gospel singers. I-IV-V-I progression (Ab-Db-Eb-Ab) with passing diminished approach. 6/8 or 4/4 at 70-85 BPM (slow groove).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bpmNo
barsNo
rootNoAb
octaveNo
velocityNo
bass_trackNo
drum_trackNo
start_beatNo
unit_indexNo
choir_trackNo
organ_trackNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

With no annotations provided, the description carries full behavioral transparency burden. It details the four tracks created and their musical roles, key, progression, tempo range, and time signatures. However, it omits side effects like interaction with existing project state.

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?

Front-loaded with main purpose, followed by bullet-pointed track details. Some verbose contextual sentences ('Gospel music — the foundation...'), but overall well-structured and informative.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given 11 parameters and no schema descriptions, the description adequately covers the arrangement components and key parameters. However, gaps remain for several parameters (e.g., unit_index, start_beat) that are not explained, affecting agent's ability to use correctly.

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?

Schema description coverage is 0%, so the description must compensate. It explains some parameters (bpm, root, tempo range, track numbers) but not all 11 (e.g., unit_index, start_beat, octave details). Partial but insufficient coverage.

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 gospel arrangement with specific instruments (shuffle drums, walking bass, Hammond organ, choir). It distinguishes from sibling genre-specific tools by detailing the gospel style components.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

While the description implies usage for traditional gospel arrangements, it lacks explicit when-to-use or when-not-to-use guidance compared to other genre arrangement tools. No alternatives or prerequisites are mentioned.

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