Skip to main content
Glama

mcp_opendaw_create_techno_arrangement

Generate a full techno arrangement with drums, sub-bass drone, and percussive stabs across three tracks. Controls tempo, bars, root note, and track indices.

Instructions

Create a full techno arrangement — drums + sub-bass drone + percussive stabs across 3 tracks.

Berlin/Detroit techno with hypnotic, minimalist elements locked together:

  • Track 0: Drums — relentless four-on-floor with industrial hats and claps, the engine

  • Track 1: Bass — sustained sub-bass drone with root shifts per phrase, not rhythmic but continuous — the hypnotic foundation that drives the groove underground

  • Track 2: Stabs — percussive atonal stabs on off-beats, the signature Detroit sound

At 130 BPM (default), this creates the classic warehouse techno feel. The sub-bass drone is the key difference from house — instead of off-beat bass notes, it's a continuous low-end that shifts root notes across phrases, creating tension and release.

bpm: Tempo (125-145, default 130 = classic techno). bars: Arrangement length (8-32, default 8). Techno needs longer forms. root: Root note (C is the classic techno key for sub-bass). octave: MIDI octave for sub-bass (2 = C2=36, low but audible). unit_index: AU index with note tracks. drum_track / bass_track / stab_track: Track indices.

Returns notes created per track and total.

Example: create_techno_arrangement(bpm=130, root="C", bars=8) create_techno_arrangement(bpm=138, root="A", bars=16)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bpmNo
barsNo
rootNoC
octaveNo
velocityNo
bass_trackNo
drum_trackNo
stab_trackNo
start_beatNo
unit_indexNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

No annotations are provided, so the description carries full burden. It describes what is created (notes on three tracks) and mentions the return value. However, it doesn't clarify whether existing notes are cleared, prerequisites like track existence, or potential side effects, leaving some behavioral gaps.

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 well-structured, starting with purpose, then track details, then parameter list, and examples. It is verbose but each sentence adds value, and examples aid understanding.

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?

The description covers genre and track roles well, and mentions return values. However, it lacks details on prerequisites (e.g., track requirements), side effects, and two parameters are unexplained. With output schema present, return value explanation is not required but still helpful.

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?

With 0% schema coverage, the description adds significant value by explaining 8 of 10 parameters (bpm, bars, root, octave, unit_index, track indices) with ranges, defaults, and context. It omits velocity and start_beat, which are minor gaps.

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 techno arrangement' and specifies the three tracks (drums, sub-bass drone, stabs), distinguishing it from siblings like create_house_arrangement by emphasizing techno-specific elements and the difference from house.

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 provides context on when to use this tool (for techno) and contrasts with house music, offering implicit guidance. However, it doesn't explicitly list alternatives or when not to use it, which is acceptable given many sibling tools.

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