Skip to main content
Glama

boomerang

Plays a video forward then backward to create a looping ping-pong effect. Set the number of repeats to control how many back-and-forth cycles the clip makes.

Instructions

Forwards then backwards, like a boomerang. times = how many back-and-forths.

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": {
      "video": "<video>"
    },
    "name": "boomerang"
  }
}

Input Schema

NameRequiredDescriptionDefault
timesNo
videoYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.4/5.0
Behavior2/5

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

Annotations already declare a non-destructive, closed-world mutation. The description adds the core effect (forward then reverse playback), but does not disclose whether the source video is modified in place or a new video is produced, what happens to audio, or what the result looks like — meaningful gaps for a mutation tool.

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 short sentences, front-loaded with the effect semantics followed by the only explained parameter. Nothing is wasteful, though the terseness borders on under-specification rather than true economy.

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

Completeness2/5

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

For a two-parameter mutation tool with no output schema and no schema descriptions, the definition leaves key unknowns: the meaning/format of 'video', whether output is a new file or in-place change, and any duration or file-size implications of 'times'. It is not sufficient on its own.

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

Parameters2/5

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

Schema description coverage is 0%, so the description carries the full burden. It nicely defines 'times' as the number of back-and-forth cycles, but says nothing about the required 'video' parameter — whether it is an ID, filename, or path — leaving half the parameters undocumented.

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

Purpose3/5

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

"Forwards then backwards, like a boomerang" conveys the effect semantics, so an agent can infer this applies a ping-pong playback effect to a video. However, there is no explicit verb+resource statement (e.g. 'apply a forward-then-reverse effect to a video'), and the phrase is metaphorical rather than operational.

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?

No when-to-use, when-not-to-use, or alternative guidance is given. The agent must guess whether this is the right tool versus siblings like extend_clip or change_speed, and no prerequisites or constraints are stated.

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