Skip to main content
Glama

mcp_opendaw_balance_track_velocities

Balance MIDI velocities across multiple tracks to set relative mix levels using presets or custom targets.

Instructions

Balance velocities across multiple tracks — MIDI mix leveling.

Sets relative velocity levels across multiple note tracks so they sit correctly in the mix. Unlike scale_velocity (one track at a time), this operates on multiple tracks simultaneously and establishes the relative balance between them.

Presets:

  • "mix_balanced" — all tracks equal (~0.75). Neutral starting point.

  • "drums_forward" — drums loudest (0.95), bass (0.80), harmony (0.65), lead (0.70). Hip-hop, rock, electronic.

  • "vocal_forward" — vocal/lead loudest (0.95), pads (0.60), bass (0.75), drums (0.80). Pop, ballad, singer-songwriter.

  • "pads_quiet" — pads very quiet (0.50), arp (0.65), bass (0.80), drums (0.90), lead (0.85). Ambient, cinematic.

  • "bass_heavy" — bass loudest (0.95), drums (0.85), lead (0.70), harmony (0.55). Reggae, dub, trap.

  • "custom" — use target_velocities parameter (comma-separated 0-1 values, one per track in track_indices order).

The tool reads current average velocities, computes scale factors to reach targets, and applies them. Original relative dynamics within each track are preserved (multiply mode).

track_indices: Comma-separated track indices (e.g. "0,1,2,3"). preset: One of the presets above, or "custom". target_velocities: For custom mode — comma-separated target avg velocities (e.g. "0.9,0.7,0.6,0.8"). Must match track_indices count. region_index: Region (-1 = first, -2 = all regions).

Returns per-track velocity stats before/after.

Example:

Balance 4 tracks: drums, bass, pads, lead

balance_track_velocities(0, "0,1,2,3", preset="drums_forward")

Custom: drums=0.9, bass=0.7, pads=0.5, lead=0.8

balance_track_velocities(0, "0,1,2,3", preset="custom", target_velocities="0.9,0.7,0.5,0.8")

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
presetNomix_balanced
unit_indexYes
region_indexNo
track_indicesYes
target_velocitiesNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

No annotations are provided, so the description must fully explain behavior. It states that the tool 'reads current average velocities, computes scale factors to reach targets, and applies them' and that 'Original relative dynamics within each track are preserved (multiply mode).' It also notes that it returns per-track velocity stats before/after, giving a complete picture of 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 well-structured with sections: summary, presets list, behavioral notes, parameter explanations, and a usage example. Every sentence adds value without redundancy. It is concise yet comprehensive.

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 5 parameters, 0% schema coverage, no annotations, and an output schema (which isn't shown but exists), the description covers all necessary aspects: purpose, when to use, behavior, parameters, return value, and examples. It also differentiates from a sibling tool. The description is complete for effective use.

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%, so the description must compensate. It explains each parameter: track_indices as comma-separated indices, preset as one of five named presets or 'custom', target_velocities for custom mode, and region_index with defaults. It also provides a detailed example showing how to use parameters together.

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 'Balances velocities across multiple tracks — MIDI mix leveling.' It uses a specific verb ('balance velocities') and resource ('multiple tracks'), and distinguishes itself from the sibling tool 'scale_velocity' which operates on one track at a time.

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?

The description explicitly tells when to use this tool (for relative balance across multiple tracks) and when not (use scale_velocity for a single track). It provides multiple presets and a custom mode, along with examples of how to use the tool with different parameter combinations.

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