sequence_animation
Creates a sequence of GSAP animations by defining targets, animations, and delays. Automatically plays the sequence in order.
Instructions
序列动画
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| autoPlay | No | ||
| sequence | Yes |
Creates a sequence of GSAP animations by defining targets, animations, and delays. Automatically plays the sequence in order.
序列动画
| Name | Required | Description | Default |
|---|---|---|---|
| autoPlay | No | ||
| sequence | Yes |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the full burden but conveys no behavioral information. The agent cannot determine if this tool creates, plays, or defines an animation, nor what side effects or authentication needs exist.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is extremely short but fails to provide necessary information, making it under-specified rather than concise. It does not earn its place as a useful description.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool's complexity (nested object parameters, no output schema, and many sibling tools), the minimal description is completely inadequate. The agent cannot effectively select or invoke this tool correctly.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 0%, and the description adds no meaning to the parameters autoPlay and sequence. The parameter semantics are entirely undocumented, leaving the agent without guidance on parameter usage.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description '序列动画' is a tautology, simply restating the tool name 'sequence_animation' in Chinese. It lacks a verb or specific resource, providing no clear indication of what the tool does.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance is given on when to use this tool versus the numerous sibling tools such as create_timeline_animation or create_stagger_animation. The description offers no context for appropriate usage.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/Lillard01/GSAP-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server