stykanimate-mcp

add_figure_instance

Places a new instance of an existing figure type or preset prop into every keyframe of the animation scene, with optional position, scale, color, and transparency settings.

Instructions

Places a new instance of an existing figure type or preset prop (e.g., broadsword, round shield, enemy stickman) into the animation scene across all keyframes.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "add_figure_instance"
  }
}

Input Schema

Name	Required	Description
`rootX`	No	Initial X position on canvas (default: center)
`rootY`	No	Initial Y position on canvas (default: center)
`scale`	No	Scale multiplier (default: 1.0)
`preset`	No	Spawn a character or prop rig preset: "blue", "walker", "sword", or "shield"
`colorRgb`	No	Color tint [r, g, b]
`figureTypeId`	No	ID of existing figure type in document (optional if preset is used)
`transparency`	No	Transparency 0-255 (0 = opaque)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.1Nov 3, 2026

TDQS

B3.1/5.0

Behavior2/5

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

With no annotations, the description carries the full behavioral burden, yet the only real disclosure is 'across all keyframes', which is useful (the instance spans the entire timeline, not just the current frame). It says nothing about permissions, undo/reversibility, whether the new instance becomes selected, or what is returned — significant gaps for a mutation tool with zero annotation coverage.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single sentence that front-loads the verb and resource and wastes no words. The examples are short and directly aid recognition of what counts as a figure or prop.

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

Completeness3/5

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

For a seven-parameter, all-optional creation tool with no annotations and no output schema, the description covers purpose and timeline behavior but omits the return value (e.g., the new instance's identifier) and the preset-versus-figureTypeId interaction. Adequate but with clear gaps an agent would hit on first call.

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 coverage is 100%, so the schema already documents all seven parameters, making 3 the baseline. The description's prop examples loosely map onto the preset enum (blue, walker, sword, shield), but it adds no detail on precedence between preset and figureTypeId or on how rootX/rootY defaulting works.

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?

States a specific verb and resource: 'Places a new instance of an existing figure type or preset prop' into 'the animation scene', with concrete examples (broadsword, round shield, enemy stickman). The phrase 'existing figure type' implicitly separates it from define_stick_rig, but the contrast is never made explicit.

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?

There is no when-to-use or when-not-to-use guidance, and no alternatives are named among the seven siblings. The only usage signal is indirect — 'existing figure type' hints that a rig must already exist, but the agent must infer that prerequisite rather than being told.

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

Deploy Server