Skip to main content
Glama

mcp_opendaw_rotate_notes

Rotate notes in a region cyclically by a specified number of steps, shifting positions, pitches, or both to create melodic variations and patterns.

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 of disclosure. It thoroughly explains the cyclic shift mechanics, wrap-around behavior, axis semantics, and preserve_pitch_contour effect. It falls short of mentioning whether other note properties (velocity, duration) are preserved or if the operation is reversible, which would be valuable context.

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 clear opening sentence, a detailed shift explanation, a brief musical context paragraph, and an organized Args section. While moderately long, each section adds value and the content is front-loaded with the core purpose.

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 (6 parameters, no annotations), the description covers the core operation, parameters, and usage contexts comprehensively. It does not address edge cases like empty regions or prerequisites, but overall it provides enough for an agent to decide when and how to invoke the tool.

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?

The input schema has zero description coverage (only bare titles), so the description must—and does—compensate fully. Every parameter (unit_index, track_index, region_index, rotate_by, axis, preserve_pitch_contour) is explained with meaningful details, including defaults, direction semantics, and the three axis options.

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 opens with a specific, actionable statement: 'Rotate notes in a region by N positions (cyclic shift).' This clearly identifies the action, resource, and transformation type, distinguishing it from sibling tools like reverse_notes, invert_notes, or transpose_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?

It provides clear context by mentioning compositional techniques (serialism, jazz melodic variation, electronic music pattern transformation), implying when this tool is appropriate. However, it does not explicitly state when not to use it or offer comparisons to alternatives like reverse or invert.

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-ai/opendaw-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server