Skip to main content
Glama

Motion CSS audit

audit_motion_css
Read-only

Audit pasted CSS for motion problems. Pass css (stylesheet text with @keyframes, animation and transition rules). Optional flash data you measured or know from the design: flashes_per_second, flash_area_percent (share of the screen that flashes). Flags: animation or transition of layout properties (width, height, top, left, margin, padding, font-size and similar, which force layout), paint-heavy properties, transition: all, animations or transitions with no matching prefers-reduced-motion rule, infinite animations with no animation-play-state or pause control in the CSS (WCAG 2.2.2), long durations, and flashing risk against WCAG 2.3.1 (more than three flashes in any one second, unless the flashing area is small). Flash rate from CSS is estimated from the animation duration and cannot see luminance change. Static analysis only.

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": {
      "css": "<css>"
    },
    "name": "audit_motion_css"
  }
}

Input Schema

NameRequiredDescriptionDefault
cssYesCSS to audit
flash_area_percentNoShare of screen that flashes, 0 to 100
flashes_per_secondNoFlashes per second, if known

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare readOnly/closed-world/non-destructive, and the description adds substantial context on top: the full list of what gets flagged, the WCAG 2.2.2 and 2.3.1 criteria referenced, and two honest limitations (flash rate estimated from duration, no luminance visibility). That is exactly the extra disclosure annotations cannot carry.

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?

Purpose is front-loaded and the flag enumeration reads as a compact inventory rather than filler. The single long sentence is dense but each clause carries information; minor tightening of the property list would improve it.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a static lint tool with no output schema, the description enumerates the flag categories it can return and states the analysis limits, which is everything an agent needs to call it correctly and interpret the result.

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, but the description adds real meaning beyond the schema: 'css' must contain @keyframes/animation/transition rules, and the flash params are framed as optional measured-or-known design data, clarifying when to supply them.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Opens with a specific verb and resource ('Audit pasted CSS for motion problems') and pins the scope to stylesheet text with @keyframes/animation/transition rules. An agent can distinguish this from broader siblings like check_motion or review_animation_principles without inspecting either schema.

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?

Explains what to pass (stylesheet text) and what the optional flash data represents if measured or known from design, and states the tool is static analysis only. It gives clear context for invocation but never names an alternative sibling or an explicit exclusion condition.

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