Skip to main content
Glama

render_variations

Generate 2-6 alternative versions of an existing video to choose from. Vary the seed for different results with identical settings, or adjust movement around the original while keeping the same seed.

Instructions

Several versions of an earlier video to pick from (2-6). vary: "seed" (same settings, different luck: the usual choice) or "movement" (less and more movement around the original, same seed). Returns job ids for job_status.

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

Input Schema

NameRequiredDescriptionDefault
varyNoseed
countNo
videoYes
priorityNobatch

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior4/5

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

Annotations only tell the agent this is not read-only, not destructive, and closed-world. The description adds real behavioral context beyond that: output is asynchronous job ids meant to be polled via `job_status`, the variation count is bounded to 2-6, and `seed` reuses identical settings while `movement` varies around the original. It does not mention render cost or duration, which matters for a paid GPU operation.

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?

The purpose and the count range are front-loaded, and the parameter breakdown follows immediately with no filler. The phrasing for `movement` ('less and more movement around the original') is terse to the point of ambiguity but still compact.

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?

There is no output schema, and the description correctly covers the return value (job ids for `job_status`), which is the most important omission to preempt. However, with 0% schema coverage it leaves the required `video` field and the `priority` parameter entirely unexplained, which is more gap than an agent should have to bridge.

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 for four undocumented parameters. It does well on `vary` (values, semantics, which is the default choice) and constrains `count` to 2-6, but says nothing about the required `video` input or what `priority` ('batch' default) controls.

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 states the specific action and object: producing 2-6 alternative versions of an earlier video, with the range stated explicitly. It never names or contrasts with the obvious sibling `render` or `render_batch`, so the agent must infer the distinction from the name alone.

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?

Guidance is limited to parameter choice: `vary: "seed"` is flagged as 'the usual choice', which is a genuine usage hint, and `movement` is described as exploring movement range around the original. There is no statement of when to prefer this tool over `render` or `render_batch`, nor any prerequisite or cost warning.

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