Skip to main content
Glama

mcp_opendaw_create_voice_exchange

Applies contrapuntal techniques like imitation, inversion, or retrograde to pass melodic motifs between tracks, creating dialogic textures.

Instructions

Create a voice exchange — imitative counterpoint where motifs pass between voices.

A voice exchange is a contrapuntal technique where melodic material is passed between two or more voices. Voice A states a motif, Voice B responds with the same motif (transposed, inverted, or retrograded), creating a dialogic texture. This is the foundation of fugue, canon, and Renaissance polyphony.

Unlike clone_track (exact copy) or copy_notes_to_track (direct clone), voice exchange transforms the material as it passes between voices:

  • Imitation: same motif at a different pitch level

  • Inversion: motif inverted (intervals flipped)

  • Retrograde: motif reversed in time

  • Retrograde-inversion: both reversed and inverted

  • Augmentation: motif stretched in time

  • Diminution: motif compressed in time

With swap=True, the source notes are also moved to the target register, creating a true voice exchange where the voices cross.

Args: unit_index: AU index. source_track: Source note track index (contains the original motif). source_region: Source region index (0 = first region). target_track: Target note track index (where the response goes). target_region: Target region index (0 = first region). exchange_mode: Transformation mode (imitation, inversion, retrograde, retrograde_inversion, augmentation, diminution). interval: Pitch interval for imitation (semitones). Default 7 = perfect fifth. transpose: Additional semitone transpose on top of interval. time_offset: Time offset in beats before the response starts. Default 2.0 = response begins 2 beats after source starts. duration_factor: Duration multiplier (1.0 = same, 2.0 = augmentation, 0.5 = diminution). Overrides augmentation/diminution modes. velocity_factor: Velocity multiplier for the response voice. swap: If True, also swap source notes to target register (true exchange).

Returns notes created, transformation mode, and exchange statistics.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
swapNo
intervalNo
transposeNo
unit_indexYes
time_offsetNo
source_trackNo
target_trackNo
exchange_modeNoimitation
source_regionNo
target_regionNo
duration_factorNo
velocity_factorNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

Without annotations, the description carries full burden. It details that the tool transforms motifs via imitation, inversion, retrograde, etc., and explains the swap parameter's effect. It also mentions the return value (notes created, mode, statistics). Minor missing detail on potential side effects, but overall 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 and front-loaded with purpose, but slightly lengthy due to the enumeration of transformation modes and parameter list. While every sentence adds value, minor redundancy exists (e.g., repeating 'motif passes between voices'). Still above average.

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?

The description covers all aspects needed: it explains the technique, lists transformation modes, details all parameters, and mentions return values. With an output schema existing, the return description is sufficient. The tool is complex but the description is thorough.

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%, so the description must compensate fully, which it does. It explains all 12 parameters with clear semantics, default values, and even interaction notes (e.g., duration_factor overrides modes). This adds significant meaning beyond the bare schema.

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 creates a voice exchange, a specific contrapuntal technique. It uses precise verb and resource ('Create a voice exchange') and explicitly distinguishes from sibling tools like clone_track and copy_notes_to_track.

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

Usage Guidelines5/5

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

The description explicitly contrasts with clone_track and copy_notes_to_track, stating that this tool transforms material rather than copying exactly. It provides clear context for when to use (imitative counterpoint) and when not to use (exact copies), and outlines the transformation modes.

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