Skip to main content
Glama

mcp_opendaw_displace_rhythm

Displace notes in a region by a fixed rhythmic offset: shift mode adds delay or anticipation for laid-back or pushed feel; circular mode rotates the pattern, creating new variations.

Instructions

Displace all notes in a region by a fixed rhythmic offset — laid-back, push, or circular rotation feel.

Rhythmic displacement shifts notes in time without changing their pitch or duration. This is one of the most expressive production techniques:

  • Laid-back (offset=0.0625 = 1/16 late): drums sit behind the beat, creating a relaxed, hip-hop/R&B feel (J Dilla, Questlove).

  • Pushed (offset=-0.0625 = 1/16 early): notes anticipate the beat, creating urgency and energy (rock, punk, certain jazz).

  • On-top (offset=0): reset any displacement back to original grid.

Two modes:

  • "shift" — add offset to every note's position. Notes can move past the region boundary (region duration auto-extends). Negative offset moves notes earlier; notes before position 0 are clamped to 0.

  • "circular" — rotate the pattern by offset. Notes that go past the region end wrap around to the beginning. This creates entirely new patterns from the same material — a 1/16 rotation of a straight 16th hi-hat pattern creates an off-beat pattern. The region length is preserved.

unit_index: AU index (-1 = all AUs). track_index: Note track index (-1 = all note tracks on the AU). region_index: Region index (-1 = all regions on the track). offset: Displacement in beats. Positive = later (laid-back), negative = earlier (pushed). Common values: 0.0625 (1/16), 0.125 (1/8), 0.03125 (1/32), 0.25 (1/4). Range -4.0 to 4.0. mode: "shift" (add offset to position, region may extend) or "circular" (rotate within region bounds, region length preserved).

Returns per-track note counts and displacement stats.

Example:

J Dilla laid-back drums — 1/16 note late

displace_rhythm(unit_index=0, track_index=0, offset=0.0625, mode="shift")

Urgent pushed melody — 1/32 early

displace_rhythm(unit_index=0, track_index=3, offset=-0.03125, mode="shift")

Circular rotation — new pattern from same notes

displace_rhythm(unit_index=0, track_index=0, offset=0.125, mode="circular")

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
modeNoshift
offsetNo
unit_indexNo
track_indexNo
region_indexNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

Given no annotations, the description details key behaviors: shift mode extends region, negative offset clamped at 0, circular mode wraps and preserves region length. Return stats are mentioned. No contradictions; adequately transparent.

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?

Well-structured with sections for purpose, modes, parameters, and examples. Every sentence adds value; no fluff. Front-loaded with the core action and musical intent.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Covers all essential aspects: purpose, two modes with behavioral differences, parameter details, and practical examples. With output schema existing, no need to detail return values separately. Complete for a tool of this complexity.

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 has 0% description coverage, but the description compensates fully by explaining each parameter (unit_index, track_index, region_index, offset, mode) with valid ranges, defaults, and common values. Examples further clarify parameter usage.

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's purpose: 'Displace all notes in a region by a fixed rhythmic offset.' It elaborates on modes (shift/circular) and gives concrete musical examples (laid-back, pushed), distinguishing it from sibling tools like apply_swing or quantize_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?

Provides explicit context for when to use each mode and offset value, with examples like 'laid-back' and 'pushed.' Implicitly guides when not to use (reset with offset=0), but does not explicitly name alternative tools for similar tasks.

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