Skip to main content
Glama

ab_loop

Set A and B points to repeat a section of the current media file, clear them to stop looping, or check loop status; omitting position uses current playback time.

Instructions

Control the A-B loop, which repeats a section of the current file. Set point A and point B to start looping; clear to stop. Omit position to use the current playback position.

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": {
      "action": "<action>"
    },
    "name": "ab_loop"
  }
}

Input Schema

NameRequiredDescriptionDefault
actionYesa/b set a loop bound, clear removes both, status reads them
positionNoPosition in seconds for the a/b actions. Defaults to the current position.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full behavioral burden. It does disclose state effects ('clear to stop', 'clear removes both') and scoping to 'the current file', which is real added context. It omits whether the loop persists across file changes or seeks, and whether setting B before A is legal.

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?

Three short sentences, front-loaded with what the tool controls and its purpose before the action mechanics. Nothing is redundant or padded.

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 simple two-parameter playback tool with no output schema, the description covers purpose, action flow, and the position default. The one meaningful gap is the 'status' action: with no output schema, a note on what status reports (A/B positions, whether looping is active) would close the loop.

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 100% and the enum values are already self-documented in the schema, so the baseline is 3. The description's only additional parameter guidance is restating the `position` default ('Omit `position` to use the current playback position'), which the schema already states.

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 a specific verb ('Control') and a specific resource ('the A-B loop'), then defines what that resource does ('repeats a section of the current file'). That definitional sentence is valuable because 'A-B loop' is jargon. It does not differentiate from the sibling 'stop' tool, and 'clear to stop' arguably blurs that boundary.

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?

It gives a usable workflow ('Set point A and point B to start looping; clear to stop') and a defaulting rule for `position`. However, it never says when to use this tool versus siblings like 'stop' or 'chapter_seek', nor what happens if only point A is set.

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