Skip to main content
Glama

mcp_opendaw_create_riser

Generate ascending pitch sweeps for build-up transitions in your DAW. Creates a sequence of notes with ramped velocity and customizable pitch curve.

Instructions

Create a riser — ascending pitch sweep for build-up transitions.

Generates a sequence of notes with ascending pitch from start_pitch to end_pitch over the specified length. Velocity ramps up proportionally. Useful for:

  • Build-ups before a drop/chorus

  • Transition between sections

  • Tension creation

unit_index: AU index with note track (-1 = find first AU with note tracks). track_index: Note track index within the AU. start_beat: Position in beats where the riser begins. length_beats: Duration of the riser in beats (1-16). start_pitch: Starting MIDI pitch (default 36 = C2). end_pitch: Ending MIDI pitch (default 84 = C6). steps: Number of notes in the sweep (8-128, default 32 = sixteenths over 4 beats). curve: Pitch curve — "linear" (even), "exp" (slow start, fast end), "log" (fast start, slow end). velocity: Base velocity (0-1, ramped proportionally with pitch).

Returns notes created and pitch range.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
curveNoexp
stepsNo
velocityNo
end_pitchNo
start_beatNo
unit_indexNo
start_pitchNo
track_indexNo
length_beatsNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

No annotations provided. The description discloses that it generates notes with ascending pitch and proportional velocity ramp, and returns created notes and pitch range. However, it does not specify potential side effects like overwriting existing notes or creating new tracks, which would improve transparency.

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 one-liner purpose, detailed explanation, bulleted use cases, and parameter list. It is front-loaded and informative, though could be slightly more concise by omitting redundant phrases.

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 tool has 9 parameters, no required ones, and an output schema (not shown), the description covers purpose, usage, parameters, and return value. It lacks details on error handling or creation behavior (e.g., if it creates a new region), but is largely complete for an agent.

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?

The input schema has 0% description coverage, so the description carries full burden. It explains every parameter: unit_index, track_index, start_beat, length_beats, start_pitch, end_pitch, steps, curve, velocity. It includes defaults, valid ranges (e.g., steps 8-128, curve options), and how they affect the riser, greatly aiding correct invocation.

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 riser — ascending pitch sweep for build-up transitions' using a specific verb ('Create') and resource ('riser'). It distinguishes itself from siblings like 'create_buildup' and 'automation_sweep' by focusing on pitch sweeps.

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 explicitly lists use cases: build-ups before a drop/chorus, transitions, and tension creation. While it does not mention exclusions or alternatives, the provided context is sufficient for an agent to decide when to use this tool.

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