Skip to main content
Glama

mcp_opendaw_create_dubstep_arrangement

Generate a dubstep arrangement with half-time drums, wobble bass, and lead arpeggios across three tracks at a specified tempo and key.

Instructions

Create a full dubstep arrangement — half-time drums + wobble bass + lead arp across 3 tracks.

Dubstep with all elements locked in half-time feel:

  • Track 0: Drums — half-time at 140 BPM (feels like 70): kick on 1, snare on 3, with percussive fills and ghost notes. The signature dubstep swing.

  • Track 1: Bass — wobble bass: sustained sub notes with rhythmic pitch shifts between root and octave/fifth, creating the "wub-wub" that defines the genre. Cutoff-sweep style pitch modulation via note offsets.

  • Track 2: Lead — minor arpeggio that runs through the arrangement, atmospheric and dark, complementing the wobble bass.

At 140 BPM (default), half-time means the groove feels at 70 BPM — kick on beat 1, snare on beat 3 of each bar. This is the fundamental difference from all other electronic arrangements: the half-time feel creates the heavy, swinging groove.

bpm: Tempo (135-150, default 140 = classic dubstep). bars: Arrangement length (4-16, default 8). root: Root note (G is a classic dubstep key). octave: MIDI octave for wobble bass (1 = C1=24, sub-bass territory). unit_index: AU index with note tracks. drum_track / bass_track / lead_track: Track indices.

Returns notes created per track and total.

Example: create_dubstep_arrangement(bpm=140, root="G", bars=8) create_dubstep_arrangement(bpm=145, root="F", bars=16)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bpmNo
barsNo
rootNoG
octaveNo
velocityNo
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?

Describes track behavior, rhythmic structure, and return value (notes per track and total). No annotations provided, so description carries full burden. Discloses half-time feel and pitch modulation but does not mention potential side effects like overwriting existing tracks.

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?

Front-loaded purpose, then details, then parameter list, then examples. Some repetition of BPM explanation. Well-organized but slightly verbose.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Covers musical intent and main parameters with examples. Lacks explanation for velocity, start_beat, unit_index. No output schema but describes return value. Adequate for a genre arranger but with gaps.

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 is 0%, so description must compensate. Explains bpm, bars, root, octave, and track indices with musical rationale. Misses velocity, start_beat, unit_index. Provides examples. Partially compensates but not fully.

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 'Create a full dubstep arrangement' with specific components (half-time drums, wobble bass, lead arp). Distinguishes from sibling genre arrangers by specifying dubstep and half-time feel.

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 for when to use this tool (creating dubstep arrangement with half-time feel). Implicitly contrasts with other electronic arrangements by emphasizing the genre-specific rhythm. Lacks explicit exclusions or alternatives.

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