Skip to main content
Glama

mcp_opendaw_create_variations

Create thematic variations from a source note region by applying transformations such as transpose, invert, reverse, augment, diminish, fragment, or octave shift. Each variation is written to a new region.

Instructions

Create thematic variations from an existing note region.

Reads notes from a source region and generates N variations, each written to a new region on the target track. Each variation applies a transformation: transpose, invert, reverse, augment, diminish, fragment, or octave_shift. This is the fundamental compositional technique of theme-and-variations (Bach Goldberg, Beethoven Diabelli, Brahms, jazz reharmonization).

source_unit: AU index of the source notes. source_track: Note track index within the source AU. source_region: Region index to read from (0 = first region). variations: Comma-separated variation specs. Each spec is: "transpose:N" — transpose by N semitones (e.g. transpose:5, transpose:-7) "invert" — invert around middle C (axis=60) "invert:N" — invert around pitch N "reverse" — reverse note order (keep positions relative) "augment:N" — multiply durations by N (e.g. augment:2 = double) "diminish:N" — divide durations by N (e.g. diminish:2 = halve) "fragment" — keep only notes on beats (quantize to beat boundaries) "octave_up" — shift up one octave (+12) "octave_down" — shift down one octave (-12) Example: "transpose:5,invert,reverse,augment:2,octave_down" target_unit: AU index for variations (-1 = same as source). target_track: Track index for variations (-1 = same as source). start_beat: Starting beat for first variation. spacing_beats: Gap between variations in beats (0 = each starts after previous ends).

Returns notes per variation, total notes, variation count.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
start_beatNo
variationsNotranspose:5,transpose:-3,invert,reverse,augment:2
source_unitYes
target_unitNo
source_trackYes
target_trackNo
source_regionNo
spacing_beatsNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

The description clearly states the behavior: reads source region, generates N variations, writes new regions to target track. It explains transformation formats and defaults. With no annotations, it carries the transparency burden well but omits error handling and prerequisites (e.g., source region existence).

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 well-structured: a one-line summary, process overview, parameter list with examples, and output note. It uses clear line breaks and bullet points. Length is justified by complexity; no redundancy.

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?

Given the tool's complexity (8 parameters, multiple transformations) and presence of output schema, the description covers core usage, parameters, and return values. It lacks explicit error handling or prerequisite checks but is sufficient for typical use.

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 is the sole source for parameter semantics. It thoroughly explains all 8 parameters: source_unit, source_track, source_region, variations (with format and examples), target_unit, target_track, start_beat, spacing_beats. Defaults and examples are provided.

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 starts with a clear verb+resource: 'Create thematic variations from an existing note region.' It details the process and lists specific transformations (transpose, invert, reverse, etc.), distinguishing it from siblings like create_motif_variations and create_arrangement_variation by focusing on note-level theme-and-variations.

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 implies usage for creating thematic variations from a note region with classical compositional context. It provides examples and parameter details. However, it lacks explicit when-to-use or when-not-to-use guidance relative to sibling tools, such as create_motif_variations.

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