Skip to main content
Glama

mcp_opendaw_create_buildup

Create a complete build-up combining a pitch riser and snare roll for transitions before a drop or chorus. Supports EDM, trap, techno, rock, and minimal styles.

Instructions

Create a complete build-up — riser + snare roll in one call.

Combines two transition elements for a full build-up before a drop/chorus:

  1. Pitch riser (ascending notes with velocity ramp)

  2. Snare roll (increasing density + velocity crescendo)

style: Build-up character:

  • "edm" — 1/4 snare → 1/8 → 1/16 → 32nd roll, exp riser C2→C6

  • "trap" — 1/4 snare → triplets → 32nd roll, exp riser C1→C5

  • "techno" — ride cymbal buildup + open hat crescendo, exp riser C2→C4

  • "rock" — tom roll buildup, linear riser C2→C4

  • "minimal" — just riser, no snare roll (subtle build)

unit_index: AU index (-1 = find first AU with note tracks). track_index: Note track index for riser. start_beat: Where the build-up begins. length_beats: Total build-up length (default 8 = 2 bars). velocity: Base velocity (0-1, ramped up during build).

Returns notes created for riser and snare roll.

Example:

8-beat EDM build-up before a drop

create_buildup(start_beat=0, length_beats=8, style="edm")

Then drop

create_impact(start_beat=8, impact_type="sub_boom")

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
styleNoedm
velocityNo
start_beatNo
unit_indexNo
track_indexNo
length_beatsNo

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 full burden. It discloses that the tool creates notes for riser and snare roll, details style-specific behaviors, and explains the meaning of each parameter. It does not mention whether it appends or overwrites existing notes, but overall is transparent about its operation.

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 with a brief intro, bullet points for style options, and parameter list. While it is longer than needed, every sentence adds value and there is no fluff.

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 the output schema exists, the description provides sufficient information about return values. It covers all parameters, styles, and usage context. It could mention alternative tools like create_riser or create_section_transition, but is otherwise complete.

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?

Schema coverage is 0%, yet the description provides detailed explanations and default values for all 6 parameters. For the 'style' parameter, it explicitly lists all possible values and their musical effects, which 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 that the tool creates a complete build-up combining a riser and snare roll, specifying it is for use before a drop/chorus. It distinguishes itself from siblings like create_riser and create_trap_rolls by being a combined call.

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 for when to use (before a drop/chorus) and includes a usage example with create_impact. It does not explicitly state when not to use or list alternative tools, but the example and style options give clear 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-team/opendaw-mcp'

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