Skip to main content
Glama

mcp_opendaw_create_downtempo_arrangement

Generates a downtempo/trip-hop music arrangement with boom-bap drums, deep sub-bass, melancholic chords, sparse melody, and atmospheric pads at 85 BPM in a minor key.

Instructions

Create a downtempo/trip-hop arrangement — 85 BPM Bristol sound.

Downtempo/trip-hop emerged from Bristol, UK (early 1990s) — a fusion of hip-hop breaks, dub bass, atmospheric samples, and melancholic vocals. Key characteristics:

  • 80-90 BPM, laid-back, heavy groove

  • Boom-bap drums with swing, vinyl crackle aesthetic

  • Deep, melodic sub-bass with long notes

  • Minor key, dark/jazzy harmony (m7, m9, half-diminished)

  • Atmospheric pads, Rhodes piano, sparse melodies

  • Sample-based, cinematic, nocturnal mood

Creates 5 tracks:

  1. Drums (track_index): Boom-bap pattern — kick on 1 & 3, snare on 2 & 4, swung hats, ghost notes, occasional fills

  2. Bass (track_index+1): Deep sub-bass with long sustained notes, melodic movement, octave drops

  3. Chords (track_index+2): Minor 7th/9th Rhodes-style chords, sparse, on beat 1 of every 2 bars

  4. Melody (track_index+3): Sparse, melancholic minor key melody with wide intervals and long rests

  5. Atmosphere (track_index+4): Sustained pad notes, root and fifth, very low velocity, cinematic texture

Default key: D minor (classic trip-hop key — Portishead, Massive Attack).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bpmNo
barsNo
key_rootNoD
velocityNo
start_beatNo
unit_indexNo
track_indexNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It details output structure (5 tracks) and musical style, but does not disclose side effects (e.g., where tracks are added, any overwrite behavior, or project state dependencies).

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 well-organized (action, genre context, track breakdown) but includes verbose historical and musical exposition that may not be necessary for tool invocation. Could be trimmed without losing core guidance.

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?

Given 7 parameters with 0% schema coverage and no annotations, the description should provide more actionable parameter guidance. It explains the genre and track roles well but lacks details on how to adjust parameters to customize the arrangement. Existence of output schema is noted but not described.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, yet the description only clarifies bpm (85 default) and key_root (D minor), and indirectly implies track_index from track descriptions. Parameters like velocity, start_beat, unit_index, and bars are not explained, leaving significant 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 opens with a clear action verb and specific genre ('Create a downtempo/trip-hop arrangement — 85 BPM Bristol sound'), and the detailed characteristics and track list distinguish it from sibling genre tools like create_lofi_arrangement or create_ambient_arrangement.

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 implies usage through genre specification and musical characteristics, but does not explicitly state when not to use (e.g., against other genres) or name alternatives among the many sibling tools.

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