Skip to main content
Glama

mcp_opendaw_create_liquid_dnb_arrangement

Create a liquid drum & bass arrangement across four tracks: smooth breakbeat, melodic sub-bass, lush chords, and soulful lead melody. Customize tempo, bars, root, and velocity.

Instructions

Create a full liquid drum & bass arrangement across 4 tracks.

Liquid DnB is the smooth, melodic cousin of DnB. Instead of Reese bass and Amen breakbeat fury, liquid uses:

  • Track 0: Smooth breakbeat (gentler ghost notes, more flowing hats)

  • Track 1: Melodic sub-bass (jazzy movement, not just root stabs)

  • Track 2: Lush extended chords (maj7/min9, not plain triads)

  • Track 3: Soulful jazz-influenced lead melody

Think LTJ Bukem, Calibre, High Contrast, Hospital Records.

bpm: Tempo (160-185, default 174). bars: Arrangement length (4-32, default 8). root: Root note (default F = classic liquid key). octave: Bass octave (2 = sub-bass range). velocity: Base velocity (default 0.75 = smoother than DnB's 0.85).

Example: create_liquid_dnb_arrangement(bpm=174, root="F", bars=8) create_liquid_dnb_arrangement(bpm=170, root="Am", bars=16, velocity=0.7)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bpmNo
barsNo
rootNoF
octaveNo
velocityNo
pad_trackNo
bass_trackNo
drum_trackNo
start_beatNo
unit_indexNo
melody_trackNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

No annotations provided; description carries full burden. Discloses track roles and musical style, but does not mention whether existing content is overwritten, whether tracks are created, or other side effects. Partially transparent.

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?

Description is appropriately sized, front-loaded with purpose and track overview. Genre background and examples are helpful but slightly verbose. Well-structured.

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?

Output schema exists, so return value explanation is unnecessary. Description covers core functionality and main parameters, though misses some less-used parameters. Adequate for typical usage.

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 coverage 0% but description explains 5 key parameters (bpm, bars, root, octave, velocity) with defaults and examples. Six parameters (pad_track, bass_track, etc.) are undocumented, relying solely on schema names. Incomplete 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?

Description clearly states 'Create a full liquid drum & bass arrangement across 4 tracks' with specific track roles. Distinguishes from sibling 'create_dnb_arrangement' by specifying liquid DnB characteristics and references to artists.

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?

Examples show typical usage. Implicitly contrasts with general DnB tool via description of liquid style, but lacks explicit when-not-to-use guidance or comparisons to specific siblings.

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