Skip to main content
Glama

set_clip_warp

Change an audio clip's warp settings and sync loops to song tempo by supplying the loop's original BPM; omitted settings remain unchanged.

Instructions

Change an audio clip's warp settings; anything left out stays as it is. Give a loop's own tempo as original_bpm (sample names often carry it, "...131...") and it follows the song tempo: warping goes on and the warp markers are rebuilt for that tempo.

Parameters:

  • track_index: An audio track

  • clip_index: Session slot, or position in get_arrangement_clips

  • location: "session" (default) or "arrangement"

  • warping: Warp on or off

  • warp_mode: "beats" (drums), "tones" (monophonic), "texture", "re_pitch" (vinyl-like), "complex" / "complex_pro" (full mixes), or 0–6

  • original_bpm: The loop's own tempo

  • pitch_coarse: Transposition in semitones (−48…48)

  • pitch_fine: Detune in cents (−50…50)

  • gain: Clip gain 0.0–1.0 (the reply shows it in dB)

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "track_index": "<track_index>",
      "clip_index": "<clip_index>"
    },
    "name": "set_clip_warp"
  }
}

Input Schema

NameRequiredDescriptionDefault
gainNo
warpingNo
locationNosession
warp_modeNo
clip_indexYes
pitch_fineNo
track_indexYes
original_bpmNo
pitch_coarseNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.1.1

TDQS

A4/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does real work: it discloses that omitted fields are preserved, and that supplying original_bpm turns warping on and rebuilds the warp markers for that tempo — a consequential, partly destructive side effect an agent must know before calling. It stops short of covering what happens to existing markers when warping is set to false, or any error/permission conditions.

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 behavior paragraph is front-loaded and the parameter block is a scannable list, which is appropriate for nine parameters. A few phrases are slightly wordy ("sample names often carry it, '..._131_...'") but they earn their place by making the original_bpm rule concrete.

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?

For a nine-parameter mutation with no annotations, the definition covers partial-update semantics, the key side effect, and full parameter meaning; the output schema exists so return values need not be spelled out, and the one return detail mentioned (gain shown in dB) is a useful bonus. Gaps remain around failure modes and the interaction between warping=false and existing markers, but nothing essential for a correct call is missing.

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 coverage is 0%, so the description must compensate entirely, and it does: every one of the nine parameters is documented with meaning, and several carry extra value beyond the schema — warp_mode's string enum with musical intent plus the numeric 0–6 alternative, explicit ranges for pitch_coarse (−48…48) and pitch_fine (−50…50), the gain 0.0–1.0 range with a note that the reply reports dB, and the clip_index disambiguation between session slot and arrangement position.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Opens with a specific verb and resource: "Change an audio clip's warp settings," and immediately qualifies the scope with partial-update semantics. It is distinguishable from get_clip_warp (read) and edit_warp_markers (marker-level edits), though it never names those siblings, and the broader reach into pitch/gain is only visible via the parameter list.

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

Usage Guidelines3/5

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

Usage is implied rather than stated: the original_bpm paragraph explains a specific scenario (a loop whose tempo is embedded in its sample name) and the effect of supplying it, which is genuine conditional guidance. However, there is no explicit when-to-use vs. when-to-use-an-alternative guidance, and nothing tells the agent when to prefer edit_warp_markers or set_clip_loop instead.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools