Skip to main content
Glama

mcp_opendaw_time_warp_notes

Scale note positions and durations to create half-time or double-time effects without altering the DAW's BPM. Warp notes by a factor from 0.1 to 8.0, with anchor options for start or zero.

Instructions

Warp note positions and durations by a factor — half-time / double-time / custom stretch.

Scales both the position and duration of every note in a region by warp_factor. Unlike scale_durations (which only changes note length, not position), this moves notes in time — creating true half-time (0.5×) or double-time (2.0×) feel without changing the DAW's BPM.

Half-time (0.5): notes spread out — a 1-bar pattern becomes 2 bars. Classic for trap, lofi, and creating build-ups before a drop. Double-time (2.0): notes compress — a 2-bar pattern becomes 1 bar. Useful for intensifying a section or creating fills.

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). warp_factor: Time scaling factor. 0.5 = half-time, 2.0 = double-time, 0.25 = quarter-time, 1.5 = 1.5× stretch. Range 0.1-8.0. origin: Anchor point for the warp — "start" (region start), or "zero" (position 0). "start" preserves relative spacing from region start. "zero" warps from absolute zero.

Returns per-track modification counts and new region extent.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
originNostart
unit_indexNo
track_indexNo
warp_factorNo
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 provided, the description fully discloses behavior: scales both position and duration, moves notes in time without changing BPM, describes warp_factor range and meaning, explains the origin anchor point, and mentions return value (modification counts, region extent). No contradictions.

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?

The description is well-structured: a concise introductory sentence followed by bullet-style explanations of parameters and behavior. It is front-loaded with key information and every sentence adds value without redundancy.

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?

Given the complexity of the tool (warp factor, origin, multiple indexes), the description covers all essential behavioral and input aspects. Output schema exists, and the description also mentions return values. No gaps or unanswered questions.

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 explains all five parameters (unit_index, track_index, region_index, warp_factor, origin) with defaults, ranges, and behavioral meaning. For example, it clarifies that -1 means 'all' and describes the effect of each origin value. This fully compensates for the missing schema 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 warps note positions and durations by a factor, with specific examples (half-time, double-time). It distinguishes from the sibling tool scale_durations by noting that this tool moves notes in time rather than just changing length.

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 scenarios (half-time, double-time, custom stretch) and contrasts with scale_durations. It also mentions genre use cases (trap, lofi). However, it doesn't explicitly state when not to use this tool or list alternative tools beyond scale_durations.

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