Skip to main content
Glama

mcp_opendaw_create_trance_arrangement

Create a full trance arrangement with four tracks: driving drums, rolling off-beat bass, supersaw arp, and pluck lead at a specified tempo between 128-145 BPM.

Instructions

Create a full trance arrangement — driving drums + rolling bass + supersaw arp + pluck lead across 4 tracks.

Uplifting trance with the signature euphoric energy — fundamentally different from other electronic genres:

  • Track 0: Drums — driving four-on-floor: kick on every quarter (hard, consistent), clap on 2 & 4, open hat on off-beats (0.5, 1.5, 2.5, 3.5). The relentless pulse of trance — harder than synthwave, faster than house. Optional snare rush buildup on last bar of each 4-bar phrase.

  • Track 1: Bass — rolling off-beat pattern: 8th notes on the "and" of every beat (0.5, 1.5, 2.5, 3.5), NOT on the quarter. Creates the "rolling" feel that drives trance forward. Root → octave alternation per bar. Different from house (off-beat stabs) — trance bass is sustained 8ths.

  • Track 2: Supersaw arp — layered chord stabs on quarter notes: root position triad (root + third + fifth) played as 16th-note arpeggio pattern per beat. The euphoric wall of sound. i-VI-III-VII progression.

  • Track 3: Pluck lead — staccato synth plucks: short melodic phrases following chord changes, mostly off-beat with occasional downbeats. The "-answer" to the supersaw's "call". Echo-like spacing.

Uses the classic trance progression i-VI-III-VII (Am-F-C-G transposed) — same as synthwave but faster and euphoric, not nostalgic. The energy is in the supersaw arp (wall of sound) and rolling bass (relentless 8ths).

At 138 BPM (default), this creates classic uplifting trance — fast, driving, euphoric. The rolling off-beat bass is the fundamental difference from all 12 other arrangements: house has off-beat stabs (short), techno has sub drones (sustained), synthwave has 16th arpeggios (melodic), trance has rolling 8ths (driving, off-beat, sustained).

bpm: Tempo (128-145, default 138 = classic uplifting trance). bars: Arrangement length (8-16, default 8). Must be multiple of 4. root: Root note (F is a classic trance key — Fm). octave: MIDI octave for bass (2 = F2=41, standard trance bass register). unit_index: AU index with note tracks. drum_track / bass_track / arp_track / lead_track: Track indices.

Returns notes created per track and total.

Example: create_trance_arrangement(bpm=138, root="F", bars=8) create_trance_arrangement(bpm=140, root="C", bars=16)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bpmNo
barsNo
rootNoF
octaveNo
velocityNo
arp_trackNo
bass_trackNo
drum_trackNo
lead_trackNo
start_beatNo
unit_indexNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

No annotations provided, so description carries full burden. It discloses per-track patterns, default values, and output summary (notes per track and total). However, it does not clarify whether existing track content is overwritten or appended, missing a key behavioral aspect. Overall, very detailed but leaves some edge cases unaddressed.

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: purpose first, then track-by-track details, genre contrasts, parameter list, examples. Some redundancy in contrasting with other genres, but each sentence adds value. Could be slightly tighter.

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 11 parameters, no annotations, and output schema present, the description covers genre-specific context thoroughly, differentiates from siblings, and provides examples. Missing parameter explanations for velocity/start_beat/unit_index and no mention of existing track handling. Complete for the core use case but not fully exhaustive.

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?

Schema coverage is 0%, so description must explain parameters. It explains 8 of 11 parameters (bpm, bars, root, octave, drum_track, bass_track, arp_track, lead_track) with meaningful context (e.g., 'root: Root note (F is a classic trance key — Fm)'). Missing descriptions for velocity, start_beat, and unit_index. Good overall coverage but not exhaustive.

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 trance arrangement with specific track roles (drums, bass, supersaw arp, pluck lead). It explicitly differentiates trance from sibling genres (house, techno, synthwave) by contrasting musical characteristics like bass pattern and energy, making the purpose distinct among many 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?

Provides clear context on when to use (uplifting trance) and specifies parameters (bpm 128-145, bars multiple of 4, root note F). Implicitly contrasts with other genre tools. Does not explicitly state when not to use, but sibling differentiation is strong enough.

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