Skip to main content
Glama

change_speed

Adjust a video's playback rate from 0.1x to 8x to create slow-motion or sped-up clips. Provide the video and a speed value, where 0.5 is half speed and 2 is twice as fast.

Instructions

0.5 = half speed (slow motion), 2 = twice as fast. 0.1 to 8.

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>",
      "speed": "<speed>"
    },
    "name": "change_speed"
  }
}

Input Schema

NameRequiredDescriptionDefault
speedYes
videoYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.6/5.0
Behavior2/5

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

Annotations declare a non-destructive mutation, but the description adds nothing behavioral: it doesn't say whether the change is applied in place or produces a new video, whether audio pitch/time is affected, or whether the source is modified irreversibly. For a write operation, that is a substantive gap beyond what annotations cover.

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, front-loaded sentences with no filler. The terseness is efficient, though the space is spent on the parameter scale rather than on stating the tool's function.

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?

With no output schema, 0% schema coverage, and only terse annotations, the description should carry the burden. It omits what the tool does to the video, the format of the `video` argument, and any effect on audio, which is inadequate for a two-parameter mutation tool.

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 description coverage is 0%, so the description must compensate. It does a good job on `speed`, giving example values and the 0.1–8 range, but says nothing about the `video` parameter (ID vs. URL vs. 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?

The description never states a verb+resource like 'change a video's playback speed'; the purpose is only inferable from the name and the phrase '(slow motion)'. An agent can guess it manipulates speed, but the definition itself does not declare the operation.

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 guidance on when to use this versus siblings such as boomerang, extend_clip, or fade, and no mention of prerequisites. The only content is numeric value interpretation, leaving usage entirely to inference.

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