Skip to main content
Glama

mcp_opendaw_create_phase_shift

Creates a phase-shifted copy of a region that gradually accumulates a time offset per bar, mimicking Steve Reich phasing. Adjust shift per bar, direction, and number of bars.

Instructions

Create a phase-shifted copy of a region — Steve Reich phasing.

Copies the source phrase and places it on a parallel track (or cross-track) with a gradually accumulating time offset. Each bar, the copy shifts by shift_per_bar beats, creating the classic "slipping" phase pattern of minimalism.

Steve Reich's "It's Gonna Rain", "Piano Phase", and "Clapping Music" use this technique. Also the foundation of techno loop phasing, ambient drift, and IDM polyrhythmic evolution.

Unlike displace_rhythm (single fixed offset), phase_shift creates a SECOND copy that drifts further each bar — the two streams start in unison and gradually separate.

Args: unit_index: Audio unit index track_index: Note track index with source phrase region_index: Region index (-1 = first region) shift_per_bar: Time shift per bar in beats (0.03125-0.5, default 0.0625 = 1/16 note per bar). Smaller = slower drift, larger = faster separation. bars: Number of bars to generate (2-16, default 8). Each bar is one repeat of the source phrase with cumulative offset. direction: Phase drift direction — "forward": copy moves later each bar (lags behind) "backward": copy moves earlier each bar (anticipates) cross_track: If >= 0, place the phased copy on this track. If -1 (default), creates a new track on the same AU for the copy. Recommended: use cross_track for explicit control. velocity_scale: Velocity multiplier for the phased copy (0.1-1.0, default 0.85 — slightly softer to distinguish from the original).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
barsNo
directionNoforward
unit_indexYes
cross_trackNo
track_indexYes
region_indexNo
shift_per_barNo
velocity_scaleNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

No annotations provided, so description carries full burden. Describes creation of a second copy, placement on parallel/cross-track, gradual drift per bar, direction, and parameter effects. Does not explicitly state side effects (e.g., track creation implications) or permission needs, but sufficiently transparent for a non-destructive operation.

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?

Well-structured: starts with title sentence, then explanation of effect, historical context, sibling contrast, then detailed parameter list. Each sentence adds value. Slightly verbose but not wasteful; could be trimmed slightly but effective.

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 complexity (8 parameters, specific phasing technique), the description covers concept, parameters, and sibling differentiation well. Output schema exists, so return values not needed. Missing edge cases like error handling or restrictions, but overall adequate for an AI agent to use 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 fully explains all 8 parameters with ranges, defaults, examples, and recommended values. Adds meaning beyond the schema's titles and types, covering unit_index, track_index, region_index, shift_per_bar, bars, direction, cross_track, and velocity_scale.

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 phase-shifted copy using Steve Reich phasing, with a specific verb 'Create' and resource 'phase-shifted copy of a region'. It explicitly distinguishes itself from the sibling 'displace_rhythm' by contrasting single fixed offset versus gradually drifting copy.

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?

Provides clear context for when to use this tool (for gradual phase shifting) and explicitly contrasts with 'displace_rhythm' as an alternative. Includes recommendations for the cross_track parameter. However, no explicit 'when not to use' or list of scenarios.

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