openDAW MCP

mcp_opendaw_reverse_notes

Reverse the order of notes in a region while preserving durations and velocities. Swap note positions so the last becomes first.

Instructions

Reverse the order of notes in a region — retrograde variation.

Swaps note positions so the last note becomes first and vice versa. Durations and velocities are preserved; only positions are mirrored.

unit_index: AU index. track_index: Note track index. region_index: Region index (-1 = all regions on the track).

Returns count of notes reversed.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "unit_index": "<unit_index>",
      "track_index": "<track_index>"
    },
    "name": "mcp_opendaw_reverse_notes"
  }
}

Input Schema

Name	Required	Description	Default
`unit_index`	Yes
`track_index`	Yes
`region_index`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.386.0Aug 4, 2026

TDQS

A4.2/5.0

Behavior4/5

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

With no annotations, the description carries the full burden of behavioral disclosure. It states that durations and velocities are preserved while only positions are mirrored, and that region_index -1 targets all regions. It also notes the return value (count of notes reversed), which provides useful context beyond the name.

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 front-loaded with the main action, then gives essential behavioral details and parameter definitions. It is reasonably concise with no filler, though the parameter lines could arguably be more detailed without harming readability.

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?

For a simple transformation tool, the description covers the operation, preservation rules, scope of region_index, and return value. Since an output schema exists, the description does not need to describe return structure. The context is complete for an agent to decide and invoke the tool correctly.

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

Parameters4/5

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

Schema coverage is 0%, so the description must compensate. It provides one-line explanations for each parameter: unit_index is the AU index, track_index is a note track index, and region_index has an explicit default meaning. This goes beyond the bare schema titles, though 'AU index' could be more fully explained.

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 opens with 'Reverse the order of notes in a region — retrograde variation', which clearly identifies the operation and resource. It distinguishes from sibling tools like rotate_notes or invert_notes by specifying the exact transformation and its musical name, so an agent can select it appropriately.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies when to use the tool via the phrase 'retrograde variation', but it does not explicitly compare with alternatives or state exclusions. There is no mention of when not to use it, such as for rotating notes instead of reversing. The guidance is implied by the purpose rather than spelled out.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server