Skip to main content
Glama

get_clip_loop

Retrieves a clip's loop switch, loop brace, start and end markers, and actual playback range in beats or seconds. Also reports arrangement position for arrangement clips.

Instructions

A clip's loop switch, loop brace and start/end markers, and what actually plays. Beats, except seconds for an unwarped audio clip ("units" says which). Arrangement clips also report their place in the song.

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_loop"
  }
}

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

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the full disclosure burden; it does add genuinely useful behavior by explaining that values are in beats except seconds for unwarped audio clips, that a 'units' field resolves which, and that arrangement clips also report song position. It does not confirm read-only safety, describe error behavior for invalid indices, or mention anything about how the loop brace relates to start/end markers when they conflict.

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?

Two tight sentences plus a three-item parameter list, with no filler and the resource identified up front. Minor deduction for the fragmented noun-phrase opening, which reads like a clipped list rather than a declarative statement of what the tool does.

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 three-parameter read tool with an output schema present, the description covers the semantics an agent actually needs: which clip is targeted, how location changes indexing, and what units the loop values carry. The absence of annotations is only partly compensated, since nothing states the operation is non-mutating.

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

Parameters4/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, and it largely does: location is clarified to 'session' (default) or 'arrangement' even though the schema has no enum, and clip_index is explained as a session slot or a position in get_arrangement_clips, which resolves a real ambiguity. Only track_index is left as the bare 'The track'.

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 names the specific resource it reads: a clip's loop switch, loop brace, start/end markers, and actual playback state, plus arrangement position. That is concrete enough to distinguish it from siblings like get_clip_warp or get_arrangement_clips, though it never states an explicit verb (the 'get' is only in the name) and the phrase 'what actually plays' is slightly opaque.

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 use this versus set_clip_loop (the obvious counterpart) or versus get_arrangement_clips, and no prerequisites or exclusions. The only usage signal is indirect, coming from the location parameter note that clip_index is a session slot or a position in get_arrangement_clips.

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