Skip to main content
Glama

mcp_opendaw_expand_intervals

Expand or compress melodic intervals in a note track by a factor to widen or narrow the melody, with anchor and scale snapping options for motivic development.

Instructions

Expand or compress melodic intervals by a factor.

Multiplies the interval between each consecutive pair of notes by factor. Values >1 widen the melody (small steps become leaps), values <1 narrow it (leaps become steps). The first note's pitch is kept as anchor (or centered around the mean pitch).

This is a fundamental transformation in motivic development:

  • factor=2.0: seconds become thirds, thirds become fifths

  • factor=0.5: thirds become seconds, fifths become thirds

  • factor=1.5: gentle expansion, more expressive contour

Args: unit_index: Audio unit index track_index: Note track index region_index: Region index (-1 = first region) factor: Interval multiplier (0.25-4.0). 1.0=no change, 2.0=double all intervals, 0.5=halve all intervals. anchor: Anchor point — "first" = keep first note pitch, expand from there, "center" = keep mean pitch, expand symmetrically, "last" = keep last note pitch, expand backwards. snap_to_scale: Scale name for snapping results ("major", "minor", "dorian", "phrygian", "lydian", "mixolydian", "locrian", "harmonic_minor", "melodic_minor", "" = no snapping, chromatic result). root: Root note for scale snapping (C, C#, D, ... B).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
rootNoC
anchorNofirst
factorNo
unit_indexYes
track_indexYes
region_indexNo
snap_to_scaleNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

With no annotations, the description carries full burden. It explains anchor behavior (first note kept, or mean centered), the effect on intervals, and snap-to-scale option. It doesn't detail side effects like reversibility or whether it modifies in place, but overall provides solid transparency.

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 summary, examples, and parameter list. It is slightly lengthy but necessary given the parameter count, and front-loads the key purpose. Every sentence adds value.

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 7 parameters, no annotations, and presence of output schema, the description covers inputs comprehensively. It implies modification of notes in the region but doesn't explicitly state the output or side effects (e.g., whether notes are replaced). Still robust for most use cases.

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 coverage is 0%, but the description fully documents all 7 parameters: unit_index, track_index, region_index, factor, anchor, snap_to_scale, and root. It includes defaults, range for factor (0.25-4.0), and explanations for each anchor and scale option.

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 it expands or compresses melodic intervals by a factor, with concrete examples for different factor values. It distinguishes itself from sibling tools like transpose (which shifts all notes equally) and invert by focusing on interval multiplication.

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 context as 'a fundamental transformation in motivic development' and gives example factors for typical uses. However, it does not explicitly state when not to use this tool or compare directly to alternatives beyond the implicit differentiation.

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