Skip to main content
Glama
1425sd

spine-mcp

by 1425sd

spine_generate_animation_json

Reads a Spine JSON skeleton and generates a modified copy with basic animation keyframes selected from a natural-language goal. Writes enhanced JSON and manifest, leaving original unchanged.

Instructions

Generate a modified Spine JSON copy by adding basic animation keyframes to an existing skeleton. Supports breathing, head_float, tail_swing, blink, paw_wave, logo_bounce, and floating by reading bones, slots, skins, and animations from sourceJsonPath. Use this for Photoshop-to-Spine JSON or existing exported Spine JSON. It only writes JSON and generation.manifest.json; it does not open Spine, import, export, pack textures, automate UI, bind mesh, edit weights, or modify .spine binaries.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
loopNoWhether the generated keyframes should be loop-friendly. Spine JSON stores loop behavior at playback time, so this is recorded in the manifest.
durationNoAnimation duration in seconds. Defaults to 2.
userGoalYesNatural-language animation goal used to select basic JSON animation timelines.
overwriteNoWhen false, stop if outputJsonPath exists or animationName already exists. When true, overwrite those generated targets.
animationNameNoAnimation name to add under animations. Defaults to "generated_loop".generated_loop
characterTypeNoOptional character hint such as "cat", "mascot", "logo", or "generic".
outputJsonPathYesDestination JSON file where the modified copy with generated animation will be written.
sourceJsonPathYesSource Spine JSON file to read. It is preserved unchanged.
Behavior4/5

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

With no annotations, the description must fully disclose behavior. It states that the tool only writes JSON and generation.manifest.json, reads from sourceJsonPath, supports various animations, and respects overwrite logic. However, it does not mention error handling or side effects beyond file writing, which is a minor gap.

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?

The description is a single paragraph that efficiently conveys purpose, supported animations, usage context, and exclusions. It is front-loaded with the main action and contains no unnecessary repetition, though it could be slightly more structured with bullet points for readability.

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?

Given no output schema, the description should clarify what the tool returns after execution. It states it writes to outputJsonPath and manifest, but does not explicitly mention that the tool returns a success message or the generated file path. This is a minor completeness gap.

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 all parameters are already documented. The tool description adds minimal extra value beyond listing supported animation types and usage context. Baseline of 3 is appropriate since the schema does the heavy lifting.

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 that the tool generates a modified Spine JSON by adding basic animation keyframes. It lists supported animations and explicitly distinguishes what it does not do, such as opening Spine or importing/exporting, which differentiates it from siblings like spine_add_simple_animation and spine_build_animation_from_json.

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

Usage Guidelines5/5

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

The description provides explicit guidance on when to use the tool: 'Use this for Photoshop-to-Spine JSON or existing exported Spine JSON.' It also lists specific supported animations and clearly states what the tool does not do, helping the agent avoid misuse.

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