Skip to main content
Glama

mcp_opendaw_create_lofi_arrangement

Create a complete lofi hip-hop arrangement with boom-bap drums, jazzy chords, mellow bass, and sleepy melody at any tempo and key.

Instructions

Create a full lofi hip-hop arrangement — boom-bap drums + jazzy chords + mellow bass + sleepy melody.

Lofi hip-hop (Nujabes / J Dilla / chillhop) — warm, dusty, mellow:

  • Track 0: Drums — boom-bap: kick on 1 and "and-a" of 2, snare on 2 and 4, laid-back 16th hi-hat with swing. No rush — behind the beat. Vinyl crackle character (lower velocity, humanized).

  • Track 1: Bass — mellow root notes with occasional octave/fifth walks. Long, sustained, warm. No aggression.

  • Track 2: Chords — jazzy 7th/9th voicings (maj7, min9, dom9) with soft attacks and gentle arpeggiation. The harmonic signature of lofi: extended chords, not triads.

  • Track 3: Melody — sparse, sleepy pentatonic phrases. Long notes, space between phrases. The "nodding off" quality.

At 78 BPM (default), this creates the classic chillhop pocket — slow, warm, behind-the-beat. ii-V-I jazz-influenced harmony (Dm7-G7-Cmaj7 in F major) gives that nostalgic, bittersweet quality.

bpm: Tempo (70-90, default 78 = chillhop sweet spot). bars: Arrangement length (4-16, default 8). root: Root note (F is a classic lofi key — warm, midrange). octave: MIDI octave for bass (3 = F3=53, warm lofi bass). unit_index: AU index with note tracks. drum_track / bass_track / chord_track / melody_track: Track indices.

Returns notes created per track and total.

Example: create_lofi_arrangement(bpm=78, root="F", bars=8) create_lofi_arrangement(bpm=82, root="D", bars=16)

Input Schema

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

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

With no annotations provided, the description fully discloses the tool's behavior: it creates notes on specific tracks, describes the musical content for each track, and specifies return value (notes per track and total). No contradictions with any structured fields.

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 lengthy but well-structured with bullet points, musical breakdown, and examples. Each part adds value, though it could be slightly more concise. Still efficient for the complexity.

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?

Given 11 parameters, 0% schema coverage, no annotations, and an output schema, the description is highly complete: it explains the style, each track's role, parameter details, defaults, ranges, and examples. It covers all necessary context for correct invocation.

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

Parameters5/5

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

The input schema has 0% description coverage, but the description explains every parameter with defaults, ranges, and musical context (e.g., 'bpm: Tempo (70-90, default 78)', 'octave: MIDI octave for bass'). This adds significant value beyond the schema.

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 'Create a full lofi hip-hop arrangement' with specific musical details for each track, effectively distinguishing it from sibling tools that create other genres (e.g., create_blues_arrangement). The verb 'create' and resource 'arrangement' are precise.

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 explains when to use this tool (for lofi hip-hop arrangements) and provides examples and parameter ranges. While it doesn't explicitly state when not to use it, the context of sibling tools covering other genres implies appropriate usage. Lacks explicit alternatives but still clear.

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