Skip to main content
Glama

mcp_opendaw_create_blues_arrangement

Generates a 12-bar blues arrangement with shuffle drums, walking bass, dominant 7th chords, and blues scale lead at any tempo.

Instructions

Create a full blues arrangement — shuffle drums + walking bass + dominant 7th chords + blues scale lead.

Classic 12-bar blues — the foundation of American popular music:

  • Track 0: Drums — shuffle/blues groove: kick on 1 and 3, snare on 2 and 4, shuffled hi-hats (triplet feel). The blues shuffle is the heartbeat — not straight 8ths, not full triplets, but the in-between "swing" that makes blues feel like blues.

  • Track 1: Bass — walking bass: quarter notes outlining the chord changes. I-I-I-I | IV-IV-I-I | V-IV-I-V. Each beat walks to the next chord tone — the jazz/blues lineage.

  • Track 2: Chords — dominant 7th voicings (I7, IV7, V7). The blues doesn't use triads — every chord is a 7th. Stab pattern on beats 1 and 3, with shuffle feel.

  • Track 3: Lead — blues scale (root, b3, 4, b5, 5, b7) with blue notes. Bends, slides, long held notes. The "crying guitar" quality — pentatonic minor with the flat 5 blue note for tension.

At 120 BPM (default), this is the classic Chicago blues tempo. At 90 BPM, it's a slow blues (B.B. King). At 140, it's a fast shuffle (Stevie Ray Vaughan).

The 12-bar form: I-I-I-I-IV-IV-I-I-V-IV-I-V. This is the most important chord progression in popular music — the DNA of rock, jazz, soul, and R&B.

bpm: Tempo (70-160, default 120 = classic Chicago blues). bars: Arrangement length (must be multiple of 12 for full blues form. 12 = one chorus, 24 = two choruses, default 12). root: Root note (A is the most common blues key — guitar-friendly). octave: MIDI octave for bass (2 = A2=45, standard blues 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_blues_arrangement(bpm=120, root="A", bars=12) create_blues_arrangement(bpm=90, root="E", bars=24) # slow blues, 2 choruses

Input Schema

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

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

The description details the musical output but does not disclose operational behaviors such as whether existing track data is overwritten, what happens with invalid track indices, or if the tool is idempotent. No annotations are provided, so the description carries the full burden, which it partially meets.

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 verbose and includes extensive musical education, which may be informative but could be more concise. The key information is front-loaded, but the later sections repeat concepts (e.g., the 12-bar progression).

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?

The description comprehensively covers the tool's purpose, musical structure, parameter usage, and examples. It provides sufficient context for an AI agent to understand the output and constraints, especially given that an output schema exists (not shown here).

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?

With 0% schema description coverage, the description compensates by explaining most parameters (bpm, bars, root, octave, tracks) and providing examples. However, parameters like 'velocity' and 'start_beat' are not described, leaving some gaps.

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 blues arrangement with specific instrumentation (drums, bass, chords, lead) and musical details. It distinguishes itself from sibling arrangement tools by focusing on the blues genre and 12-bar form.

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?

The description provides extensive musical context and parameter usage but lacks explicit guidance on when to use this tool versus sibling arrangement tools. It implies usage through genre specificity but does not directly advise against using it for non-blues styles.

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