Skip to main content
Glama
1425sd

spine-mcp

by 1425sd

spine_build_animation_from_existing_project

Adds simple keyframe animations to existing Spine skeletons by interpreting a natural-language goal and using learned presets, outputting a playable .spine project.

Instructions

Build simple animation keyframes on an existing Spine JSON or .spine project. Writes to outputDir, imports into .spine, exports, and can open the result. Requires sourceJsonPath or spineProjectPath. Not for mesh, IK, weights, or UI automation.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
userGoalYesNatural-language animation goal. The tool uses this with learned corpus presets to choose simple keyframes for the existing skeleton.
imagesDirNoOptional folder containing images referenced by sourceJsonPath. When provided, it is copied to outputDir/images and the generated JSON uses that images folder.
outputDirYesDirectory where the modified JSON, imported .spine project, copied images, and exported files should be written.
overwriteNoWhen false, stop if outputDir already exists. When true, overwrite generated files inside outputDir without deleting files outside it.
exportModeNoDeprecated alias for exportSettingsPath. Must be a Spine export settings .json file path. Mode strings like "json" or "json+pack" are not accepted by Spine 3.8.75.
projectNameYesProject file base name to generate inside outputDir, without path separators.
knowledgeDirNoDirectory containing learned knowledge files. Defaults to G:\spine-mcp\knowledge. If missing, built-in fallback presets are used.G:\spine-mcp\knowledge
characterTypeNoCharacter category used to choose default layout and animation presets.
openAfterBuildNoWhen true, open the generated .spine project after import/export without waiting for Spine to exit.
sourceJsonPathNoOptional existing Spine JSON file, for example a Photoshop to Spine exported skeleton JSON. When provided, this takes precedence over spineProjectPath.
spineProjectPathNoOptional existing .spine project. When sourceJsonPath is not provided, the tool exports this project to temporary JSON first using the Spine CLI.
exportSettingsPathNoPath to a Spine export settings .json file used with -e. If omitted, tools that can build a .spine project skip the final export step.
sourceExportSettingsPathNoPath to a Spine export settings .json file used to export spineProjectPath to JSON before analysis. Required when using spineProjectPath unless exportSettingsPath/exportMode also points to a JSON export setting.
Behavior4/5

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

No annotations are provided, but the description reveals the tool's actions (writing to outputDir, importing, exporting, opening) and that it is not for mesh/IK/weights/UI automation. It does not cover permission or rate-limit details, but given the absence of annotations, it provides reasonable transparency.

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: first explains the core purpose and what the tool does, second gives requirements and limitations. No filler, effectively front-loaded.

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

Completeness4/5

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

With 13 parameters and no output schema, the description covers the tool's purpose and key constraints (required inputs, exclusions). It doesn't detail return values, but that is acceptable given the absence of an output schema. Provides sufficient context for selection.

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

Parameters4/5

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

Schema description coverage is 100%, so baseline is 3. The description adds value by clarifying that one of sourceJsonPath or spineProjectPath is required (though both are optional in schema), explaining characterType enum purpose, and warning about exportMode deprecation. This goes beyond the schema descriptions.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool builds simple animation keyframes on an existing Spine JSON or .spine project, and lists actions (writes, imports, exports, opens). It also distinguishes by stating 'Not for mesh, IK, weights, or UI automation,' which differentiates it from potential siblings.

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

Usage Guidelines4/5

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

The description explicitly requires 'sourceJsonPath or spineProjectPath' and excludes complex animation types. However, it does not directly compare to sibling tools like spine_build_animation_from_json, leaving some ambiguity about when to choose one over the other.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/1425sd/spine-MCP'

If you have feedback or need assistance with the MCP directory API, please join our Discord server