motionspec
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| motion_catalogA | Returns the catalog of verified motion primitives (names, purpose, parameter schemas, defaults) plus the authoring rules for writing a MotionSpec. Call this FIRST, then write the spec yourself and validate it with motion_validate (motion_compile runs in the CLI or with a key on the hosted endpoint). |
| motion_validateA | Checks a MotionSpec against the schema, the primitive allow-list, parameter bounds and injection rules. Fail-closed: returns ok=false with precise errors. Returns {ok, errors, warnings, deprecations, catalogVersion}. IMPORTANT: warnings[] carries the WCAG 2.2.2 / reduced-motion findings and can be non-empty while ok=true — a spec that compiles is not automatically accessible. Use to pre-check a spec before compiling. |
| motion_compileA | Validates (fail-closed) and deterministically compiles a MotionSpec into production-ready vanilla-GSAP JavaScript and CSS, with enforced prefers-reduced-motion fallbacks and a performance-budget report. Same spec always yields identical code. Returns {ok, js, css, report} or {ok:false, errors}. |
| motion_auditA | Static motion-a11y checker: fetches a URL's HTML + linked stylesheets and scans the CSS for (1) animation/transition without a prefers-reduced-motion guard, (2) animated non-transform/opacity properties, (3) infinite animations with no pause path, (4) /autoplay >5s. Runtime motion (WAAPI/GSAP/JS) is disclosed as 'not audited (V2)'. Returns {ok, score, findings, summary, badge, disclosures, markdown}; a clean site earns the badge 'reduced-motion-safe'. Does network I/O (openWorldHint). |
| motion_statsA | Summary of routing/compile telemetry (counts per outcome). Escalation clusters indicate which new primitive the catalog needs next. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
Most tools have clearly distinct roles: catalog, audit, and stats are unambiguous, while validate and compile overlap because compile also performs fail-closed validation. The descriptions mitigate this by positioning validate as a pre-check and compile as the production step, leaving only minor ambiguity.
All tools share a consistent motion_ prefix and usesnake_case, which makes the set predictable. However, the second element mixes nouns like catalog, audit, and stats with verbs like validate and compile, deviating slightly from a strict verb_noun convention.
Five tools is a compact, deliberate set that covers authoring, validation, compilation, accessibility auditing, and telemetry. Each tool has a clear role in the workflow with no apparent redundancy or bloat.
The core pipeline of fetching the catalog, validating a spec, and compiling it into production assets is fully supported, with audit and stats as complementary capabilities. The only notable gap is that motion_audit cannot inspect runtime JavaScript animation, though it explicitly discloses this as a V2 limitation.