Skip to main content
Glama

inspect_animation_opportunities

Inspect headings, links, overflow, and Web Animations timing to identify motion opportunities and capture an evidence screenshot for planning.

Instructions

Inspect actual headings, links, overflow and Web Animations timing for motion planning; writes evidence screenshot.

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": {
      "url": "<url>",
      "output": "<output>"
    },
    "name": "inspect_animation_opportunities"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYes
widthNo
heightNo
outputYes
recordNo
actionsNo
fullPageNo
recordFpsNo
showCursorNo
recordMaxSecondsNo
waitMillisecondsNo
allowInteractionsNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior3/5

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

The annotations declare readOnlyHint=false and destructiveHint=false, and the description usefully explains why: it writes an evidence screenshot. That is genuine added context. But the description is silent on the substantial behavioral machinery exposed by the schema—recording mode, the actions sequence, and the fact that there is an interaction gate—so an agent cannot learn here that actions likely require allowInteractions.

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?

A single dense sentence that front-loads the resource and appends the side effect, with no filler. It is compact and scannable. The terseness is arguably part of the parameter-semantics problem rather than a structural flaw.

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

Completeness2/5

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

For a 12-parameter tool with a rich action union and a recording mode, one sentence is not enough. The output schema spares it from explaining return values, but the interaction/recording capabilities and the gating relationship between allowInteractions and actions are entirely undocumented. An agent would have to reverse-engineer call shape from the raw schema.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across 12 parameters, so the description carries the full burden and it does not deliver. The items it lists (headings, links, overflow, timing) are inspection outputs, not parameters; url, output, width/height, record, recordFps, recordMaxSeconds, showCursor, allowInteractions and the actions union are all left to bare names. An agent could easily misread 'record' or 'allowInteractions' without guidance.

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?

Names a specific verb ('Inspect') plus concrete targets: headings, links, overflow and Web Animations timing, and states the goal ('for motion planning'). It also discloses a side effect ('writes evidence screenshot'), so the agent knows this is not a pure read. It does not name a sibling to distinguish itself from near neighbours like capture_page or analyze_visual_rhythm, keeping it out of 5 territory.

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

Usage Guidelines3/5

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

The phrase 'for motion planning' implies the phase in which this tool belongs, which is useful context. However, there is no explicit when-to-use vs when-not, and no mention of the alternative inspection tools it competes with. The agent must infer selection from the sibling list rather than the description.

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