Skip to main content
Glama

mcp_opendaw_create_jazz_arrangement

Generate a jazz arrangement with swing drums, walking bass, comping piano, and horn melody using ii-V-I harmony. Customizable tempo, bars, root key, and track assignments.

Instructions

Create a full jazz arrangement — swing drums + walking bass + comping piano + horn across 4 tracks.

Jazz with swing feel and ii-V-I harmony — fundamentally different from all other arrangements:

  • Track 0: Drums — swing ride pattern (spang-a-lang), brush snare ghost notes, comping on bass drum. The signature jazz ride cymbal pattern with swung 8th notes — the triplet feel that defines jazz.

  • Track 1: Bass — walking bass: quarter notes that walk through the chord changes using chord tones and approach notes. ii-V-I aware, creating smooth voice leading through the changes.

  • Track 2: Piano — comping: syncopated chord stabs using shell voicings (root + third + seventh) and rootless voicings. Frequent rests — comping is about space as much as notes.

  • Track 3: Horn — lead melody: a simple bluesy head over the changes, using blue notes (flatted thirds and fifths) and swing.

At 120 BPM (default), this creates a medium-up swing feel. The ii-V-I progression is the fundamental jazz chord change — every other genre uses different harmony. Swing 8ths (triplet feel) is the rhythmic signature that separates jazz from all straight-time genres.

bpm: Tempo (60-200, default 120 = medium swing). bars: Arrangement length (4-32, default 8). Jazz benefits from longer forms. root: Root note (F is a classic jazz key — great for horns). octave: MIDI octave for bass (2 = F2=41, standard jazz bass register). unit_index: AU index with note tracks. drum_track / bass_track / piano_track / horn_track: Track indices.

Returns notes created per track and total.

Example: create_jazz_arrangement(bpm=120, root="F", bars=8) create_jazz_arrangement(bpm=180, root="Bb", bars=12)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bpmNo
barsNo
rootNoF
octaveNo
velocityNo
bass_trackNo
drum_trackNo
horn_trackNo
start_beatNo
unit_indexNo
piano_trackNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

Detailed description of musical output per track (drum pattern, bass walking, piano comping, horn melody). Discloses return value (notes per track and total). No annotations provided, so description carries full burden; however, it does not address potential side effects like overwriting existing data or permissions.

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?

Well-structured with track breakdown and parameter list, but verbose with detailed musical descriptions that could be shortened. Front-loaded with main purpose, so overall adequate but not maximally 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?

Given no annotations and low schema coverage, the description covers purpose, behavioral details per track, default settings, return value, and includes examples. Missing some parameter explanations (velocity, start_beat), but otherwise comprehensive for a complex arrangement 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?

Despite 0% schema description coverage, the description provides meaningful defaults and ranges for most parameters (bpm, bars, root, octave, track indices). Misses 'velocity' and 'start_beat', which weakens completeness, but still adds significant semantic value.

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?

Clearly states it creates a full jazz arrangement with specific instrumentation (swing drums, walking bass, comping piano, horn). Emphasizes unique jazz features (swing feel, ii-V-I harmony) to distinguish from sibling genre-specific arrangement tools.

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?

Explicitly describes when to use (for jazz with swing feel and ii-V-I harmony) and contrasts with other arrangements. Implicitly guides via unique characteristics, but lacks explicit 'when not to use' or alternative suggestions.

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