Skip to main content
Glama

mcp_opendaw_map_velocity_by_pitch

Map MIDI note velocity to pitch for natural dynamics. Use modes like higher_quieter to make low notes louder or lower_quieter for brighter leads.

Instructions

Map velocity based on pitch — expressive dynamics from note height.

Adjusts note velocity proportionally to pitch position. High notes get quieter, low notes get louder (or vice versa). This simulates natural acoustic instrument behaviour where register affects perceived intensity.

Modes:

  • "higher_quieter" — high notes quieter, low notes louder (piano natural, orchestral mockups). Default. Kick drum louder than hi-hat.

  • "lower_quieter" — low notes quieter, high notes louder (lead synth patches, bell-like timbres where highs cut through).

  • "bell_curve" — loudest in the middle register, quieter at extremes (vocal range, mid-range instruments like guitar/violin).

  • "inverse_bell" — quietest in the middle, louder at extremes (experimental).

intensity: 0-1, how much pitch affects velocity (0 = no change, 0.5 = moderate, 1.0 = full effect). At 0, velocities are unchanged.

The formula for "higher_quieter": relative_pos = (pitch - pitch_ref) / 48 (48 = 4 octaves range) factor = 1.0 - relative_pos * intensity new_vel = current_vel * factor (clamped to min/max)

pitch_ref: MIDI pitch that serves as the neutral point (no change). 60 = C4 (middle C). Adjust for your instrument's register.

Use cases:

  • Make flat MIDI velocities sound more natural (piano, orchestra)

  • Drum kits: kick (low pitch) louder than hi-hat (high pitch)

  • Lead synth: highs cut through more (lower_quieter)

  • Vocal range emphasis (bell_curve around pitch_ref=64)

unit_index: AU index. track_index: Note track index. region_index: Region (-1 = first, -2 = all regions). mode: higher_quieter / lower_quieter / bell_curve / inverse_bell. intensity: 0-1, strength of pitch-to-velocity mapping. min_velocity / max_velocity: Clamp range. pitch_ref: Neutral pitch (default 60 = C4).

Returns modification summary with per-octave velocity stats.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
modeNohigher_quieter
intensityNo
pitch_refNo
unit_indexYes
track_indexYes
max_velocityNo
min_velocityNo
region_indexNo

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 reveals the transformation formula, mode differences, intensity effect, clamping behavior, and return summary. It lacks explicit caution about in-place modification or undo behavior, but the algorithm is thoroughly disclosed.

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 sections for modes, formula, use cases, and parameters. It is somewhat verbose and repeats mode and intensity details in the parameter list, but the front-loaded summary and logical organization make it easy to scan.

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?

Given real complexity (8 parameters, 4 modes, a formula, and multiple use cases), the description is remarkably complete. It covers all parameters, examples, the algorithm, and return value. The presence of an output schema further reduces the need for explanatory detail.

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 compensates by explaining every parameter including unit_index, track_index, region_index, mode, intensity, min/max_velocity, and pitch_ref. It even includes the formula showing how parameters interact, exceeding what is needed.

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 the tool maps velocity based on pitch with a specific verb and resource ('Map velocity based on pitch'). It distinguishes itself from sibling velocity tools like scale_velocity or apply_velocity_curve by emphasizing the pitch-velocity relationship and natural acoustics.

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?

Provides explicit use cases such as piano/orchestral mockups, drum kits, lead synth, and vocal range emphasis. However, it does not name alternative tools or state when not to use this tool, so it falls short of explicit exclusions.

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