Skip to main content
Glama

get_clip_warp

Retrieve an audio clip’s warp state, including warp mode, markers, transposition, gain, and length/duration, to inspect time-stretching and clip timing.

Instructions

An audio clip's warp state: warping, warp mode (and the modes on offer), warp markers (beat_time ↔ sample_time in seconds), transposition, gain, clip length and file duration.

Parameters:

  • track_index: The track

  • clip_index: Session slot, or position in get_arrangement_clips

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

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": "get_clip_warp"
  }
}

Input Schema

NameRequiredDescriptionDefault
locationNosession
clip_indexYes
track_indexYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.1.1

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full burden, yet it never states that this is a read-only/no-side-effect call, nor what happens if the clip has warping disabled or is not an audio clip. It lists output fields, but an output schema already exists, so that list adds little behavioral disclosure. Read-only behavior is only weakly implied by the word 'state'.

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?

Front-loads the returned content in a single field list, then a compact parameter block; there is no filler text. Minor deduction because the opening is a sentence fragment and the return-field list consumes most of the description despite an output schema existing.

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

Completeness3/5

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

With an output schema present, the lengthy return-value enumeration is partly redundant, and the space would have been better spent on read-only confirmation, error conditions, and when to choose this over set_clip_warp. Parameter coverage is adequate but not complete. For a simple three-parameter getter it is serviceable but leaves real gaps.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0% (titles only, no descriptions), so the description must compensate and it does partially: clip_index is clarified as a session slot versus a position in get_arrangement_clips, and location documents the 'session' default and 'arrangement' alternative that the schema does not enumerate. However, track_index is explained only as 'The track', leaving indexing base and how to obtain valid indices unspecified.

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?

The description enumerates exactly what the tool returns (warp enabled state, warp mode and available modes, warp markers with beat_time/sample_time in seconds, transposition, gain, clip length, file duration), which distinguishes it from mutation siblings like set_clip_warp and edit_warp_markers. It lacks an explicit verb ('Returns the warp state of a clip'), so the reader must infer the read operation from the noun phrase and the get_ prefix.

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

Usage Guidelines2/5

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

There is no statement of when to call this versus set_clip_warp (to modify) or edit_warp_markers (to manipulate markers), even though those siblings are the obvious confusion points. The only routing hint is embedded in a parameter note ('position in get_arrangement_clips'), which is about indexing, not tool selection.

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