Skip to main content
Glama

mcp_opendaw_humanize_notes

Add human-like variation to MIDI notes by applying subtle deviations in velocity, timing, duration, and swing, making programmed performances feel natural and expressive.

Instructions

Add human-like variation to existing notes — velocity, timing, duration, and swing.

Makes programmed MIDI feel less robotic by applying small random deviations. Works on all notes in the specified track(s)/unit(s), or globally with unit_index=-1.

unit_index: AU index (-1 = all AUs). track_index: Note track index (-1 = all note tracks on the AU). velocity_amount: Velocity deviation depth 0-1 (0.15 = ±15% of current velocity). Example: 0.05 = subtle, 0.15 = natural, 0.25 = loose. timing_amount: Timing offset depth in beats 0-1 (0.15 = up to ±15% of a 16th note = ±3.6 ticks). Example: 0.05 = tight, 0.15 = natural groove, 0.30 = sloppy. duration_amount: Duration deviation depth 0-1 (0.10 = ±10% of current duration). swing: Swing amount 0-1 (0 = straight, 0.5 = light swing, 1.0 = full triplet feel). Shifts every other 16th note later by swing * 1/3 of a 16th. seed: Random seed for reproducibility (same seed = same humanization).

Returns per-track note counts and total notes humanized.

Example: humanize_notes(unit_index=0, velocity_amount=0.15, timing_amount=0.12, swing=0.35)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
seedNo
swingNo
unit_indexNo
track_indexNo
timing_amountNo
duration_amountNo
velocity_amountNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

No annotations are provided, so the description carries the full burden. It discloses that the tool applies random deviations, affects notes in scope, uses a seed for reproducibility, and returns per-track note counts. It does not explicitly state whether modifications are in-place or whether undo is available, but it covers the core behavior and parameter effects well.

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 reasonably concise given the number of parameters. It begins with a clear one-sentence summary, then organized parameter explanations, and a practical example. Each section earns its place, though it could be slightly tightened without losing clarity.

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?

With 7 parameters, no annotations, and an output schema present, the description covers behavior, parameter semantics, scope selection, reproducibility, return values, and gives a real-world example. It is essentially complete for an agent to select and invoke the tool correctly, leaving minimal ambiguity.

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%, but the description manually explains every parameter with ranges, examples, and musical meaning (e.g., timing_amount: '0.05 = tight, 0.15 = natural groove, 0.30 = sloppy'). This fully compensates for the lack of schema descriptions and adds significant value.

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 uses a specific verb+resource: 'Add human-like variation to existing notes — velocity, timing, duration, and swing.' It clearly distinguishes from siblings by enumerating the exact dimensions modified and explicitly stating scope (all notes in specified track(s)/unit(s) or globally).

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?

Clear context is provided: the tool humanizes existing MIDI notes, works on specified tracks/units or globally, and each parameter is explained with example values. However, it does not explicitly mention when to use this tool over alternatives like humanize_pitch or apply_swing, so usage guidance is strong but not fully comparative.

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