stykanimate-mcp

create_animation_project

Initialize a new StykAnimate project with canvas size, target FPS, starter preset, and an empty frame timeline with default layers.

Instructions

Initializes a brand new StykAnimate project context (canvas dimensions, target FPS, empty frame timeline, default layers). Returns the raw initialization object mirroring StykAnimate's document model.

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": "create_animation_project"
  }
}

Input Schema

Name	Required	Description
`fps`	No	Target playback frame rate (default: 24)
`preset`	No	Starter figure preset: "blue" (StykAnimate default stickman with IK), "walker" (classic stickman), or "empty" (no figures)
`canvasWidth`	No	Canvas width in pixels (default: 960)
`projectName`	No	Human-readable project title (default: "Untitled animation")
`canvasHeight`	No	Canvas height in pixels (default: 540)
`defaultDuration`	No	Initial frame hold duration in ticks (default: 10)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.1Nov 3, 2026

TDQS

B3.3/5.0

Behavior3/5

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

With no annotations, the description carries the full disclosure burden. It does well to state the concrete side effect (an empty timeline and default layers are created) and the return shape ('raw initialization object mirroring StykAnimate's document model'). It omits important behavioral facts: whether the new project replaces or coexists with an existing one, whether the project is auto-selected as active, and whether anything is persisted to disk.

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?

Two sentences, no filler, and the operation is front-loaded before the return-value note. Nothing repeats the schema or the title, and every clause contributes new information.

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?

Since no output schema exists, the description earns credit for explaining the return value. However, for a foundational creation tool with six parameters and no annotations, it should also cover the active-project semantics and its ordering relationship to the sibling tools. As written, an agent knows what it produces but not how it fits the workflow.

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%, so the schema already documents fps, preset, canvas dimensions, projectName, and defaultDuration with defaults and bounds. The description adds only indirect signal by listing which attributes define the initialized context. Baseline 3 applies.

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 ('Initializes') with a named resource ('a brand new StykAnimate project context') and enumerates what that context contains: canvas dimensions, target FPS, empty frame timeline, default layers. That clearly separates it from the rigging, motion, and export siblings. It stops short of naming a sibling or explicitly stating its place as the pipeline entry point.

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 explicit when-to-use or when-not-to-use guidance, and no statement that this must be called before define_stick_rig, add_figure_instance, or the other siblings. The genesis role is only inferable from the word 'Initializes' and the 'brand new' phrasing, leaving the agent to guess at ordering and prerequisite relationships.

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

Deploy Server