Skip to main content
Glama

var2_motion_catalog

Read-only

READ FIRST for motion graphics (free). Choose section=styles, then section=components with query, style_id, tags, avoid_ids and recent_families for a compact ranked shortlist. component_id gives slots, physics, joins and constraints. Compose varied moments instead of repeating a whole template. The catalog includes every spec field with range + default, looks, effects, decor, media, finish, templates (params + a ready call), validated recipes, timing and pricing. Start with section=overview, then workflow; template_id = one template in full. available:false = not enabled for this user: do not offer motion.

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_motion_catalog"
  }
}

Input Schema

NameRequiredDescriptionDefault
tagsNo
limitNoShortlist size, default 12.
queryNoSemantic search, e.g. swinging sign, headline impact, product card.
formatNoDefault both.
sectionNo
style_idNo
avoid_idsNo
template_idNoA template id (section=templates): returns its params and a ready call.
aspect_ratioNo
component_idNoOne component in full, including content slots and recommended joins.
recent_familiesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added
  2. Removed
  3. Added

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, and the description is consistent with that (it is a catalog, not a builder). It adds useful behavioral context beyond the annotations: it is free, and available:false signals the tool must not be offered to the user. No output/pagination detail is given, but with annotations covering safety a 3 is fair.

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?

Front-loaded with the 'READ FIRST' directive and then flowing through sections, shortlist params, and per-id lookups. Dense and largely waste-free, though the run-on clause listing section contents is harder to parse than it needs to be.

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 an 11-param, no-output-schema discovery tool this covers what the catalog returns (spec fields with range + default, looks, effects, decor, media, finish, templates, recipes, timing, pricing) and how to navigate it. The coverage of output content substitutes for a missing output schema reasonably well, leaving only minor gaps.

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 45% schema coverage the description must compensate, and it explains most of the high-value params: section routing, query/style_id/tags/avoid_ids/recent_families feeding a ranked shortlist, component_id returning slots/physics/joins, and template_id returning params plus a ready call. It leaves format and aspect_ratio unaddressed, so it is strong but incomplete.

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?

Leads with a specific verb-like directive ('READ FIRST for motion graphics') and clarifies it is a free read/catalog tool covering spec fields, styles, effects, templates, recipes, timing and pricing. An agent can distinguish it as the discovery tool from the create/build siblings, though it never explicitly names those siblings.

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?

Prescribes a concrete sequence ('Choose section=styles, then section=components', 'Start with section=overview, then workflow') plus a critical exclusion rule: 'available:false = not enabled for this user: do not offer motion.' The two sequencing hints are slightly at odds and no explicit alternative sibling is named, keeping it below a 5.

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