Skip to main content
Glama

Plunder & Riffle Meme Engine

List motion styles

list_motion_styles
Read-only

Free discovery for the engine's banked motion craft (ported 2026-11-20): motion-design style presets (mg-styles-15), scene grammars for narrated pieces (huashu-art-motion) and measured easings (motionmaxxing). These banks ride into slideshow / hybrid generation automatically; call this to see them, or pass style (a style id like "flat-vector") to get that style's full director prompt for building a piece in it yourself. Pass section: "grammars" or "eases" for those banks in full. No key needed, nothing charged.

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

Input Schema

NameRequiredDescriptionDefault
styleNoA motion style id (from the styles list). Returns the style preset plus its full director prompt.
sectionNo"styles" (default), "grammars" or "eases".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds genuinely non-derivable context: no API key is needed, nothing is charged, and the two modes return different payloads (a bank listing versus a single style's full director prompt). It does not describe pagination or response shape, but for a static read-only catalog that is a minor gap.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The lead ("Free discovery...") is well front-loaded and the two operating modes are separated clearly. However, three sentences carry parenthetical internal catalog codes and a port date ("ported 2026-11-20") that no agent can act on, and terms like "measured easings" and "motionmaxxing" are unexplained jargon. Trimming those would sharpen the definition without losing decision-relevant content.

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?

With zero required parameters, no output schema, and read-only annotations, the description carries most of the burden and mostly meets it: it says what the three banks are and what each call mode returns. The remaining gap is that without an output schema, the shape of a styles list (ids, names, prompt text) is implied rather than stated.

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?

Schema coverage is 100%, so the baseline is 3. The description goes beyond the schema by explaining the consequence of `style` — you get that style's full director prompt for authoring in it yourself — and by giving a concrete example id ("flat-vector"). It could have clarified that `section` defaults to "styles", which the schema states but the description omits.

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 names a specific resource — the engine's banked motion style presets, scene grammars, and easings — and makes clear this tool is free discovery rather than generation. It is diminished by internal codenames (mg-styles-15, huashu-art-motion, motionmaxxing) that add noise rather than clarity, and it never explicitly names a sibling tool it is contrasted with. An agent can still tell it discovers preset data rather than creating a piece, which the create_* siblings do.

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 a real when-to-use rule: call it to see the banks, or pass `style` to fetch that style's full director prompt for building a piece yourself. It also usefully states the when-not-to: these banks ride into slideshow/hybrid generation automatically, so listing is not a prerequisite for generation. It stops short of naming which sibling to use instead when the agent actually wants to generate.

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