openDAW MCP

mcp_opendaw_duplicate_notes

Duplicate all notes in a region by shifting copies to follow the last note. Provide unit, track, and region indices to replicate the DAW's native duplicate function.

Instructions

Duplicate all notes within a region, shifting them after the last note.

Creates copies of every note in the region, shifted by (max(position+duration) - min(position)). This mirrors the DAW's native "duplicate notes" feature.

unit_index: Audio unit index (-1 = search all AUs). track_index: Note track index within the AU. region_index: Region whose notes to duplicate (0-based).

Returns count of duplicated notes and shift in beats.

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>",
      "region_index": "<region_index>"
    },
    "name": "mcp_opendaw_duplicate_notes"
  }
}

Input Schema

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

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.386.0Aug 4, 2026

TDQS

A4.4/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. It discloses the exact shift calculation, notes that it creates copies, and states the return value. This is solid, though it could mention side effects on existing notes or whether the operation is reversible.

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 concise and well-structured: a one-line summary, then the algorithm, then parameter explanations, and finally the return note. No unnecessary words.

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?

For a 3-parameter tool with an output schema, the description adequately covers the operation, parameter meanings, and return values. It could include more detail about track_index base (e.g., whether it is 0-based), but overall it is sufficiently complete.

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 description coverage is 0%, but the description compensates by explaining each parameter: unit_index supports -1 for searching all AUs, and region_index is 0-based. This adds meaning beyond the bare integer types.

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's action: 'Duplicate all notes within a region, shifting them after the last note.' It uses a specific verb (duplicate), identifies the resource (notes within a region), and explains the shift behavior. This differentiates it from siblings like duplicate_region and duplicate_note_event.

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 provides clear context by stating it 'mirrors the DAW's native duplicate notes feature,' which implies when to use it. However, it does not explicitly mention alternatives or when not to use this tool, so it falls short of a 5.

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

Deploy Server