Skip to main content
Glama

mcp_opendaw_create_gospel_arrangement

Create a complete gospel arrangement with shuffle drums, walking bass, Hammond organ, and choir harmonies.

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

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

No annotations are provided, so the description must disclose side effects. It says 'Create a full gospel arrangement' but doesn't state whether this adds new tracks, replaces existing content, or requires a specific project state. The operational behavior (mutating the project) is left implicit, which is a significant gap for a creation tool.

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 a clear purpose sentence, followed by structured bullet points for each track. While lengthy, the musical detail is relevant and not redundant. It could trim the editorializing sentence ('Gospel music — the foundation...') but overall earns its length.

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

Completeness2/5

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

For a complex 11-parameter creation tool with no annotations and no schema descriptions, the description covers the musical content thoroughly but is incomplete operationally. It doesn't mention project-level effects (additive vs. destructive), requirements, or what happens on invocation. The output schema exists, but the description still lacks integration guidance.

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 schema has 0% coverage, so the description must explain parameters. It does explain track 0-3 assignments (matching drum_track, bass_track, organ_track, choir_track defaults), mentions the default root Ab, and gives a tempo range (70-85 BPM) that relates to the bpm parameter. However, it doesn't explain bars, velocity, octave, start_beat, or unit_index, leaving many parameters underspecified.

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 gospel arrangement — shuffle drums + walking bass + Hammond organ + choir,' clearly stating the tool's function and distinguishing it from other arrangement tools. The detailed breakdown of tracks 0-3 further specifies what the arrangement includes.

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 gives clear context for when to use the tool—when a gospel arrangement is needed—and provides rich musical style details (default Ab, I-IV-V-I, tempo range). However, it doesn't explicitly exclude other styles or mention alternatives among the many sibling genre-arrangement tools, so it misses explicit when-not/alternative guidance.

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