Skip to main content
Glama

mcp_opendaw_force_scale_notes

Snap out-of-scale notes to the nearest in-scale note within a region for harmonic correction. Useful after MIDI transcription or import to fix pitch accuracy.

Instructions

Force all notes in a region into a specific scale — harmonic snap.

Finds every note that is NOT in the target scale and moves it to the nearest in-scale note. This is the harmonic equivalent of quantize_notes (which snaps timing to a grid). Useful after audio-to-MIDI transcription, random generation, or importing MIDI from unknown sources.

root_note: Root note name — C, C#, D, D#, E, F, F#, G, G#, A, A#, B. scale: Scale name — major, minor, dorian, phrygian, lydian, mixolydian, aeolian, locrian, pentatonic_major, pentatonic_minor, blues, harmonic_minor, melodic_minor. direction: How to resolve out-of-scale notes — "nearest" (closest, default), "up" (always shift up to next in-scale note), "down" (always shift down). preserve_octave: If True (default), keep notes in their original octave — only shift by 1-2 semitones. If False, allow octave jumps to find the nearest match.

Returns count of notes snapped, per-track breakdown, and which notes were changed.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
scaleNomajor
directionNonearest
root_noteNoC
unit_indexNo
track_indexNo
region_indexNo
preserve_octaveNo

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 full burden and handles it well: it explains the algorithm (moves every note not in scale to the nearest in-scale note), describes the effects of direction and preserve_octave, and states the return payload (count, per-track breakdown, changed notes). It does not explicitly mention irreversibility or how the target region is selected, but the core behavior is transparent.

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 a one-line summary, a rationale/use-case paragraph, a parameter breakdown, and a return-value note. It is slightly longer than necessary due to enumerating all scales and root notes, but that information is directly useful and not wasted. Overall it is efficient for a tool with seven parameters.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description covers the core operation, use cases, key parameters, and return value. However, it omits how the target region is identified (defaults of unit/track/region indices are not explained) and does not mention potential side effects or whether the operation is undoable. Given no annotations and no schema descriptions, this gap is notable but the description is still largely usable.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The description provides detailed semantics for four of seven parameters: root_note (with full note list), scale (with full scale list), direction (with values and meanings), and preserve_octave (behavior for true/false). However, unit_index, track_index, and region_index are completely undocumented, and schema descriptions are absent (0% coverage). This leaves a significant gap for selecting which region to operate on.

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 states a specific verb ('force'/'moves') and resource ('all notes in a region') with a clear goal: snap notes into a target scale. It further distinguishes itself from the sibling quantize_notes by calling itself the 'harmonic equivalent', making its purpose unambiguous even among many sibling tools.

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?

The description explicitly names when to use the tool ('after audio-to-MIDI transcription, random generation, or importing MIDI from unknown sources') and contrasts it with quantize_notes to clarify the harmonic-vs-timing distinction. It does not list exclusions or alternative tools beyond quantize_notes, so it falls just short of full usage guidance.

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