stykanimate-mcp

add_visual_effect

Injects impact bursts, slash arcs, or camera shake at specific timeline frames to add clear action emphasis to stick-figure animations.

Instructions

Injects dynamic action visual effects (impact bursts, sword slash arcs, screen shake) into specific timeline frames to create high-impact, production-level visuals.

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": {
      "effectType": "<effectType>"
    },
    "name": "add_visual_effect"
  }
}

Input Schema

Name	Required	Description
`scale`	No	Scale multiplier of the effect (default: 1.0)
`targetX`	No	Target canvas X coordinate for the effect
`targetY`	No	Target canvas Y coordinate for the effect
`colorRgb`	No	RGB color tuple [r, g, b] (default: bright yellow/white)
`intensity`	No	Shake amplitude in pixels (used when effectType is "camera_shake", default: 8)
`effectType`	Yes	Visual effect type: "impact_burst" (hit spark/burst), "slash_arc" (blade motion arc), or "camera_shake" (screen impact rumble)
`startFrame`	No	Keyframe index to trigger effect (0-based, default: 0)
`durationFrames`	No	How many frames the effect lasts (default: 4)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.1Nov 3, 2026

TDQS

C2.9/5.0

Behavior2/5

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

No annotations are provided, so the description must carry the full behavioral burden. "Injects" implies a mutation of the animation timeline, but the description does not state permissions required, whether the effect can be undone or removed, what response is returned, or how it interacts with existing keyframes.

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?

It is a single front-loaded sentence with no structural waste. The closing phrase "to create high-impact, production-level visuals" is mildly promotional rather than informative, but overall it is appropriately sized.

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 an eight-parameter mutation tool with no annotations and no output schema, the description is too thin. It conveys the basic purpose but omits behavioral details an agent would need, such as mutation semantics, return values, and how the effect integrates with the timeline.

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

Parameters3/5

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

Schema description coverage is 100%, and the schema already documents all eight parameters, including effectType's enum values and defaults. The description's effect examples mirror the enum descriptions but add no additional meaning about coordinates, scale, duration, or intensity.

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?

The description uses a specific verb, "Injects," and a specific resource, "dynamic action visual effects," with concrete examples (impact bursts, sword slash arcs, screen shake) and a target location (timeline frames). It is clear what the tool does, though it does not explicitly distinguish itself from sibling animation tools.

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

Usage Guidelines2/5

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

It implies that effects are added to specific timeline frames, but gives no explicit guidance on when to use this tool versus alternatives such as generate_motion_sequence or add_figure_instance. There are no prerequisites, exclusions, or workflow conditions.

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

Deploy Server