Skip to main content
Glama

explain_animations

Diagnose why an animation or transition is not smooth, does not run, or jumps. Pass an optional property to check why that property does not animate.

Instructions

Explain the animations and transitions on one element: a census of what is running right now (type, play state, timing, animated properties) plus the declared transition/animation/@keyframes rules attributed to file:line, checked against a closed ruleset of known causes. Use when an animation or transition is not smooth, does not run at all, or jumps/pops instead of animating; pass the optional property (e.g. "opacity") to check why THAT property does not animate. For a timeline of a specific click/hover (what fired, what got cancelled), use record_interaction.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
xNoViewport x coordinate — use together with y
yNoViewport y coordinate — use together with x
uidNoElement uid from a prior page_snapshot / find_elements
propertyNoCSS property you expected to animate — enables the "changes are instant" check
selectorNoCSS selector (first match) — alternative to uid
Behavior4/5

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

Since no annotations are provided, the description carries the full burden. It adequately describes what the tool does: gathers running animation information, checks against a closed ruleset, and attributes rules to file:line. It does not disclose any potential performance overhead or side effects, but the described behavior is read-only and well-scoped.

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?

The description is a single paragraph that is information-dense yet readable. It front-loads the main action and provides usage conditions. While it could benefit from bullet points or clearer separation of sections, it contains no unnecessary words and earns its place.

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?

Given the complexity (5 parameters, no annotations, no output schema), the description covers the tool's purpose, usage guidelines, and parameter hints adequately. It does not explicitly describe the output format, but the term 'census' implies a structured summary. It is complete enough for an agent to understand when and how to invoke the tool.

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% with descriptions for all 5 parameters. The description adds value by explaining that the 'property' parameter enables a specific 'changes are instant' check, which goes beyond the schema description. For x/y, it reinforces their combined use. Overall, it adds semantic context without redundancy.

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?

The description clearly states the tool's purpose: explaining animations and transitions on one element, including a census of running animations and declared rules. It distinguishes itself from sibling tool 'record_interaction' by specifying its use case for diagnosing animation issues and not for timeline recording.

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

Usage Guidelines5/5

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

Provides explicit when-to-use scenarios: when an animation is not smooth, doesn't run, or jumps/pops. Also specifies when to use an alternative: for timeline of clicks/hovers, use 'record_interaction'. This guides correct tool selection.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/mi60dev/visionaire-engine'

If you have feedback or need assistance with the MCP directory API, please join our Discord server