Skip to main content
Glama

mcp_opendaw_displace_rhythm

Displace notes in a region by a rhythmic offset to create laid-back, pushed, or rotated grooves. Choose shift mode for time-shifting or circular mode for pattern rotation.

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
Behavior5/5

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

With no annotations to fall back on, the description fully discloses behavior: it explains that pitch/duration are unchanged, that the shift mode can extend region duration and clamps notes before position 0, and that circular mode wraps notes around while preserving region length. It also mentions the return value, providing a complete behavioral picture.

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 long but well-structured with a summary, bullet points, bolded key terms, and three complete examples. While every sentence earns its place, it could be trimmed slightly without losing value, making it appropriately detailed rather than maximally concise.

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?

The description covers the tool's purpose, modes, parameter meanings, edge cases, return value, and practical examples. It is complete for a transformation tool with no annotations, and the presence of an output schema further reduces the need to document return structure in detail.

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 provides only parameter names and defaults with zero descriptions, but the description gives detailed semantics for every parameter: unit_index, track_index, region_index with -1 wildcards, offset with range and common values, and mode explaining both options. This fully compensates for the schema's lack of descriptions.

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 function: 'Displace all notes in a region by a fixed rhythmic offset' — a specific verb and resource. It goes further to explain the two modes and the musical effect, distinguishing it from siblings like rotate_notes or shift_mode by emphasizing that pitch and duration are preserved and only timing is altered.

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 context on when to use the tool: for laid-back, pushed, or on-top rhythmic feels, with examples for each. It does not explicitly name alternative tools or enumerate when not to use it, but the usage guidance is strong through the musical scenarios and mode explanations.

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