Skip to main content
Glama

var2_preview_motion_graphics

Read-only

Free, no side effects: compose catalog moments with COMPOSITION, build a TEMPLATE, or validate a hand-written SPEC exactly as the renderer sees it. For creative work prefer composition; read styles/components/joins first. Returns the normalized spec, warnings per layer, and every on-screen word with its timing (human_summary). Iterate until warnings is empty, then var2_save_motion_graphics.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "var2_preview_motion_graphics"
  }
}

Input Schema

NameRequiredDescriptionDefault
specNoA Motion Spec (catalog language + recipes).
paramsNoTemplate params (catalog template_id).
templateNoTemplate id (catalog section=templates).
compositionNo{styleId,seed,beats:[{componentId,params,durationFrames?,physics?,rotation?,scale?,join?}]}. Catalog components/styles/physics/joins define the valid values. One coherent story, varied moments.
aspect_ratioNo
duration_secondsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added
  2. Removed
  3. Added

TDQS

A4/5.0
Behavior4/5

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

The annotations only declare readOnlyHint=true; the description adds that the call is free and has no side effects, which is real cost/safety context an agent needs when deciding to iterate. It also discloses the return shape (normalized spec, per-layer warnings, human_summary word timings) despite there being no output schema, and frames it as a validate-then-save loop. It stops short of saying whether invalid input errors or simply returns warnings.

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?

Information is front-loaded: safety and modes first, then workflow, then return values. Density is high with no filler sentences, though capitalized parameter names and shorthand like 'catalog language + recipes' assume familiarity and slow a first read slightly.

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 read-only validation tool with six params, nested objects, and no output schema, the description covers purpose, workflow, and return content well enough to call it correctly. Gaps that remain are secondary: default aspect ratio/duration behavior and whether template mode requires a matching params object.

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?

With 67% schema coverage, the description meaningfully maps the three primary inputs (COMPOSITION, TEMPLATE, SPEC) to their intended workflows and tells the agent that catalog components/styles/physics/joins define valid values for composition. It says nothing about aspect_ratio or duration_seconds, whose only documentation is the enum and 1–60 range in the schema, so those remain purely structural.

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 uses a precise verb set (compose/build/validate) against a specific resource (motion graphics spec) and distinguishes its three input modes: COMPOSITION, TEMPLATE, and hand-written SPEC. It does not, however, distinguish itself from the closely-named siblings var2_motion_build or var2_motion_plan, which an agent would likely weigh against it.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives concrete routing advice ('For creative work prefer composition'), a prerequisite ('read styles/components/joins first'), and a next step ('Iterate until warnings is empty, then var2_save_motion_graphics'). What it lacks is explicit guidance on when this preview is preferred over var2_motion_build, var2_motion_plan, or direct var2_create_motion_graphics.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources