Skip to main content
Glama

mcp_opendaw_randomize_note_durations

Randomize note durations with 5 distribution modes to add controlled generative variation to note lengths.

Instructions

Randomize note durations with controllable distribution.

Adds generative variation to note lengths. Unlike humanize_notes (which adjusts timing+velocity), this focuses purely on duration with 5 distribution modes for different musical characters.

Args: unit_index: Audio unit index track_index: Note track index region_index: Region index (-1 = first region) variation: Amount of variation (0.0=no change, 0.3=moderate, 1.0=extreme). Applied as percentage of original duration. distribution: Distribution mode — "uniform" = equal probability across range, "increasing" = durations tend to get longer over time, "decreasing" = durations tend to get shorter over time, "bimodal" = clusters around short and long extremes, "jitter" = small perturbations around original values. min_duration_beats: Minimum duration in beats (0.0625=1/64th, 0.125=1/32nd, 0.25=1/16th). max_duration_beats: Maximum duration in beats (4=whole note, 8=two whole notes). preserve_total: If True, scale all durations so the total summed duration equals the original. Useful for maintaining phrase length. seed: PRNG seed for reproducibility.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
seedNo
variationNo
unit_indexYes
track_indexYes
distributionNouniform
region_indexNo
preserve_totalNo
max_duration_beatsNo
min_duration_beatsNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior2/5

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

No annotations provided, so description carries full burden. Does not disclose side effects, state changes, reversibility, or error conditions. Only describes parameters and basic function.

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?

Well-structured with purpose statement, sibling contrast, and parameter block. Distribution mode descriptions are slightly verbose but overall efficient. Front-loaded with key information.

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 9 parameters, no annotations, and existing output schema, the description covers tool function and parameters well. Missing behavioral context but otherwise complete for parameter and usage understanding.

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 coverage is 0%, but description provides extensive parameter documentation with explanations, defaults, and examples for variation, distribution, min/max durations, and preserve_total. Fully compensates for missing schema descriptions.

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?

Clear verb 'randomize' and resource 'note durations' with explicit differentiation from 'humanize_notes' (which adjusts timing+velocity). Lists 5 distribution modes for musical character, making purpose specific.

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?

States 'adds generative variation to note lengths' and contrasts with humanize_notes, providing context for when to use. However, does not mention other sibling tools like randomize_note_chance or explicitly state when not to use.

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