Skip to main content
Glama

mcp_opendaw_rotate_notes

Cyclically shift notes in a region by N positions, choosing to rotate position, pitch, or both, while optionally preserving the original melodic contour.

Instructions

Rotate notes in a region by N positions (cyclic shift).

Shifts notes cyclically — the first rotate_by notes move to the end, and the remaining notes shift left to fill the gap. This is a fundamental compositional technique used in serialism (rotational arrays — Berg, Webern), jazz melodic variation, and pattern transformation in electronic music.

Args: unit_index: Audio unit index track_index: Note track index region_index: Region index (-1 = first region) rotate_by: Number of positions to rotate (positive = left shift, negative = right shift). Wrapped modulo note count. axis: Rotation axis — "position" = rotate note order by position (notes keep pitch, positions are reassigned in rotated order), "pitch" = rotate pitches (positions stay, pitches shift cyclically among the notes), "both" = rotate both position and pitch together (true permutation — notes swap places entirely). preserve_pitch_contour: If True, after rotation adjust pitches to maintain the original melodic contour (interval sequence). Useful for melodic rotation that stays singable.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
axisNoposition
rotate_byNo
unit_indexYes
track_indexYes
region_indexNo
preserve_pitch_contourNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

With no annotations provided, the description carries the full burden. It explains cyclic shift behavior, direction (positive=left, negative=right), modulo wrapping, and the effect of each axis value. It also describes the preserve_pitch_contour option. However, it does not explicitly state whether the operation is in-place or returns a result, which is a minor gap.

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: a one-sentence summary, a detailed explanation of the operation, usage contexts, and a clear Args list. It is longer than necessary but every sentence adds value. The front-loading is good, with the core operation immediately stated.

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 complexity (6 parameters, no annotations), the description covers the tool's behavior and all parameters adequately. An output schema exists but is not described, which is acceptable because the schema provides that information. The description is complete enough for an agent to use the tool correctly.

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. It does so thoroughly: for each parameter (axis, rotate_by, unit_index, track_index, region_index, preserve_pitch_contour) it explains meaning, default values, and constraints (e.g., rotate_by wrapped modulo note count, region_index -1 meaning first region). This adds significant value beyond the 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 rotates notes in a region cyclically. It specifies the verb ('rotate'), resource ('notes in a region'), and operation ('cyclic shift'). The explanation of how the shift works (first rotate_by notes move to end) and the mention of compositional techniques distinguish it from siblings like shuffle_notes or reverse_notes.

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 usage contexts: serialism, jazz melodic variation, and electronic music pattern transformation. It gives practical guidance on when to use the tool but does not explicitly state when not to use it or suggest alternatives. This is sufficient for most agents.

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