Skip to main content
Glama

mcp_opendaw_create_acid_arrangement

Create an acid house arrangement with a squelchy TB-303 bassline, 909 drum patterns, and a hypnotic lead. Produces a complete track structure for Chicago acid house.

Instructions

Create an acid house arrangement — TB-303 squelch bassline.

Acid house is a subgenre of house music born in Chicago (1985-87) defined by the Roland TB-303 bass synthesizer with its distinctive squelchy, resonant filter sweeps. Key characteristics:

  • TB-303 bassline: monophonic, sequenced 16th notes with filter cutoff sweeps (open↔closed), accent and glide (slide) between notes. The signature "squelch" sound.

  • 909 drum machine: 4-on-floor kick, open hat on offbeats, clap on 2&4, ride cymbal

  • 125 BPM, 4/4 time

  • Minimal, hypnotic, repetitive structure with gradual evolution

  • Often in minor key with chromatic bassline movement

Creates 3 tracks:

  1. Drums (track_index): 909-style — kick on every beat, clap on 2&4, open hat on offbeats, closed hat on 16ths, ride on quarter notes

  2. Bass (track_index+1): TB-303-style 16th note pattern with chromatic movement, octave jumps, and accent patterns. Notes have varied velocity to simulate filter envelope.

  3. Lead (track_index+2): Sparse, hypnotic stab on beat 1 of every 4 bars, minor key pad-like sustained note

Default key: A minor (classic acid key).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bpmNo
barsNo
key_rootNoA
velocityNo
start_beatNo
unit_indexNo
track_indexNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

With no annotations, the description carries the full burden and discloses substantial behavior: creates 3 tracks at track_index, track_index+1, track_index+2, with detailed drum patterns, bassline velocity variations, and lead placement. It stops short of stating side effects like overwriting existing tracks or preconditions, but the creation behavior is well specified.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is well-organized: a clear opening summary, a background section on acid house, and a numbered list of track details. Every sentence serves a purpose, and the structure makes it easy to scan while providing rich context.

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?

The tool has 7 parameters and no annotations, but the description covers core creation behavior, style, and track specifics, and an output schema exists. It lacks parameter-level detail for several fields and side-effect disclaimers, but for a genre-specific arrangement generator, it is largely complete.

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 description coverage is 0%, so the description must compensate. It explains track_index (via track layout), bpm (125 BPM default), and key_root (A minor). However, bars, velocity, start_beat, and unit_index are not described, leaving several parameters unexplained.

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 states clearly: 'Create an acid house arrangement — TB-303 squelch bassline.' It specifies the verb, resource, and genre, and differentiates from sibling tools by detailing the exact track structure (drums, bass, lead) and musical characteristics. This makes the tool's purpose unmistakable.

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 strong contextual cues: genre definition, characteristic elements (TB-303, 909, 125 BPM), and track composition. This helps an agent identify when this tool is appropriate, but it does not explicitly mention alternatives or exclusion scenarios, so it misses clear 'when-not-to-use' guidance.

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-ai/opendaw-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server