Skip to main content
Glama

mcp_opendaw_create_riser

Create ascending pitch sweep risers for build-ups and transitions. Generates note sequences with ramping velocity to build tension before drops or choruses.

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
Behavior4/5

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

With no annotations provided, the description carries the full burden. It discloses that the tool generates a sequence of notes, ramps velocity proportionally, and returns the created notes and pitch range. However, it does not specify whether existing notes are preserved or overwritten, leaving a minor ambiguity about side effects.

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 front-loaded with a clear one-sentence purpose, followed by concise mechanism and use-case bullets, then a parameter list. No redundant information.

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

Completeness5/5

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

Despite lacking annotations and having 9 parameters, the description covers all parameter semantics, usage context, and return value, making it self-sufficient for an agent to select and invoke the tool correctly.

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?

All 9 parameters are individually documented with meanings, defaults, ranges, and examples (e.g., start_pitch default 36 = C2, steps 32 = sixteenths over 4 beats), fully compensating for the 0% schema description coverage.

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 defines the tool as creating a riser with an ascending pitch sweep, explicitly differentiating it from sibling tools like create_buildup by specifying the velocity ramp and pitch progression. It also provides concrete use cases.

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?

It lists specific use cases (build-ups, transitions, tension creation) but does not mention when not to use it or name alternative tools, so it lacks explicit exclusion/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-ai/opendaw-mcp'

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