stykanimate-mcp

import_legacy_asset

Reads legacy .piv and .stk asset files and converts their structural data into StykAnimate-native schema, optionally loading the result into the active project.

Instructions

Bridges the LLM to the codebase parsing layer to read standard .piv or .stk data types. Returns extracted structural configurations converted into a StykAnimate-native schema format.

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": {
      "filePath": "<filePath>"
    },
    "name": "import_legacy_asset"
  }
}

Input Schema

Name	Required	Description
`format`	No	Format hint (default: "auto" detected from file extension)
`filePath`	Yes	Local filesystem path to .stk, .piv, or .json file
`figureName`	No	Custom name to override the imported figure name
`addToProject`	No	Whether to load the imported asset into active project session (default: true)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.1Nov 3, 2026

TDQS

B3.2/5.0

Behavior2/5

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

No annotations are supplied, so the description carries the full burden. It explains parsing and conversion but omits key behavioral traits: addToProject defaults to true, so the tool may mutate the active project, and there is no mention of overwrite behavior, permissions, or failure modes.

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?

Two sentences, front-loaded with parsing purpose and then return shape, with no redundant restatement of the schema. The phrase 'Bridges the LLM to the codebase parsing layer' is a little inflated but not enough to undermine the definition.

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 4-parameter import tool with no annotations and no output schema, the description gives only a high-level return statement. It leaves out mutation/side-effect context and concrete return structure, though the schema covers parameter names well enough.

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 defines all four parameters. The description only reinforces file types (.piv/.stk) and conversion output; it adds no syntax or conditional meaning beyond the schema.

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 names the operation (import/read legacy .piv/.stk assets) and the result (converted StykAnimate-native structural configuration), which is concrete. It does not compare against siblings such as define_stick_rig or add_figure_instance, so the agent must infer routing.

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

Usage Guidelines3/5

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

It implies usage when the file is a standard .piv or .stk data type, which gives some context. However, it provides no explicit when-not conditions, no alternatives among sibling tools, and no guidance on format or addToProject decisions.

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

Deploy Server