Skip to main content
Glama

mcp_opendaw_apply_velocity_curve

Apply a deterministic velocity curve (ramp, arc, trough, or power) across MIDI notes to shape dynamics for crescendos, build-ups, and expressive phrasing.

Instructions

Apply a velocity envelope across notes — ramp, arc, trough, or custom power curve.

Maps each note's position within its region to a velocity value via a mathematical curve. Unlike humanize_notes (random variation), this applies a deterministic envelope shape — useful for build-ups, fade-ins, crescendo rolls, and expressive phrasing.

unit_index: AU index. track_index: Note track index. region_index: Region index (-1 = all regions on the track). curve_type: Curve shape:

  • "ramp_up" — linear increase from start_velocity to end_velocity

  • "ramp_down" — linear decrease from start_velocity to end_velocity

  • "arc" — rises to end_velocity then falls back to start_velocity (peak in middle)

  • "trough" — falls to start_velocity then rises to end_velocity (dip in middle)

  • "power" — exponential curve controlled by 'power' param (>1 = fast rise, <1 = slow rise) start_velocity: Velocity at curve start 0-1 (default 0.3). end_velocity: Velocity at curve end 0-1 (default 1.0). power: Exponent for "power" curve type (default 1.0 = linear). 2.0 = sharp attack, 0.5 = slow swell.

Returns per-region note counts and total notes shaped.

Examples: apply_velocity_curve(curve_type="ramp_up", start_velocity=0.2, end_velocity=1.0) # build-up apply_velocity_curve(curve_type="arc", start_velocity=0.4, end_velocity=0.95) # expressive phrase apply_velocity_curve(curve_type="power", power=2.0, start_velocity=0.1, end_velocity=1.0) # sharp attack

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
powerNo
curve_typeNoramp_up
unit_indexNo
track_indexNo
end_velocityNo
region_indexNo
start_velocityNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

No annotations are present, so the description carries the full burden. It discloses the deterministic mapping mechanism (each note's position to a velocity value), details each curve's mathematical behavior, and states the return value. It stops short of noting irreversibility or clamps on out-of-range inputs, but the disclosure is substantial.

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?

Well-structured: purpose, mechanism, differentiation, parameter specs, return value, then three practical examples. No sentence is wasted; the length is justified by the tool's complexity and 0% schema coverage.

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?

For a 7-parameter tool with no annotations and no schema-side parameter descriptions, this description is fully complete. The curve_type values are individually explained, defaults are given, return semantics are stated, and concrete usage examples anchor the behavior.

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 description coverage is 0%, yet the description documents all 7 parameters with defaults, ranges (0-1 for velocities), and behavioral meaning. 'power' gains extra semantic depth ('2.0 = sharp attack, 0.5 = slow swell'), and region_index's -1 sentinel is explained. This fully compensates for the empty 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 opens with a specific verb+resource ('Apply a velocity envelope across notes') and lists the curve variations (ramp, arc, trough, power curve). It explicitly distinguishes itself from the sibling humanize_notes, making the tool's identity unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It states when to use the tool ('useful for build-ups, fade-ins, crescendo rolls, and expressive phrasing') and explicitly contrasts it with humanize_notes for random variation. This gives an agent clear criteria for choosing this tool over an alternative.

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