Retrieve known Anime.js v4 engine parameters, optionally filtered by category, to reference valid options when writing or debugging animation code.
Lista los parámetros conocidos del motor Anime.js v4, opcionalmente filtrados por categoría.
| Name | Required | Description | Default |
|---|---|---|---|
| category | No | Categoría opcional para filtrar los parámetros. |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden. 'Lista' implies a non-destructive read, but it says nothing about ordering, completeness (what makes a parameter 'conocido'), or required permissions, and gives no sense of the returned entries.
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?
A single front-loaded sentence that names the action, the resource, the version scope, and the optional filter. Nothing extraneous.
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?
For a one-optional-param list tool with no annotations it is adequate, but with no output schema the description should sketch what a listed parameter looks like (name, category, description?) to let an agent use the result without a follow-up probe.
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 100% and the enum is fully enumerated in the schema, so baseline 3 applies. The description confirms the category filter is optional but adds no semantics (e.g., whether omitting it returns everything) beyond the schema.
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 states a specific verb and resource: 'Lista los parámetros conocidos del motor Anime.js v4'. An agent can distinguish this from get_parameter_details or search_anime_docs by the listing/enumeration nature, though it never explicitly names a sibling or contrast.
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?
'opcionalmente filtrados por categoría' implies you can call it bare for a full dump or narrow it by category, but there is no explicit when-to-use guidance or routing to get_parameter_details for deeper info on a single parameter.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.