Skip to main content
Glama

mcp_opendaw_time_warp_notes

Warp note positions and durations by a custom factor to create half-time or double-time feels without changing the DAW's BPM. Stretch notes in time for musical variation or fills.

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

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

With no annotations, the description carries the full burden. It discloses that both position and duration are scaled, explains the two origin behaviors ('start' preserves relative spacing, 'zero' warps from absolute zero), notes that the DAW BPM is unchanged, and states the return value. It doesn't mention potential edge cases like overlapping notes or undo behavior, but covers the core behavioral traits thoroughly.

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 and efficient: an opening definition, a contrast with the sibling, use cases, parameter breakdown, and a return note. Each sentence contributes value without redundancy, and the most important information is front-loaded for quick scanning.

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 is complete for selection and invocation: it covers purpose, usage guidelines, all parameters, return values, and a key behavioral distinction. Even though an output schema exists, the description still briefly mentions what is returned, making it self-sufficient for the agent.

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?

All five parameters are explained with meaningful semantics beyond the schema: index defaults (-1 meaning all), warp_factor range and examples (0.5, 2.0, etc.), and origin behaviors. This fully compensates for the 0% schema description coverage, giving the agent everything needed to set parameters correctly.

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) and a direct contrast to scale_durations. It specifies the verb (warp), resource (note positions and durations), and scope (every note in a region), effectively distinguishing it from sibling tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly names scale_durations as an alternative and explains when to use this tool (true time warp) versus that one (only duration change). It also gives concrete musical use cases for half-time (trap, lofi, build-ups) and double-time (intensifying sections, fills), providing clear context for selection.

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