Skip to main content
Glama
1425sd

spine-mcp

by 1425sd

spine_control_bones

Write custom rotate, translate, and scale timelines for existing bones into a Spine JSON copy. Controls bones via animation data without automating the Spine editor.

Instructions

Write custom rotate, translate, and scale timelines for one or more existing bones into a Spine JSON copy. Use this when you know exact bone names and keyframes. This controls bones through JSON animation data only; it does not automate the Spine editor UI, bind meshes, edit weights, create IK, or mutate .spine binaries directly.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
overwriteNoWhen false, stop if outputJsonPath exists or animationName already exists. When true, overwrite those generated targets.
boneControlsYesBone transform timelines to write. Supports multiple bones and multiple timeline types per bone.
animationNameYesAnimation name to add or overwrite.
outputJsonPathYesDestination JSON file where the modified copy will be written.
sourceJsonPathYesSource Spine JSON file to read. It is preserved unchanged.
Behavior5/5

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

Despite no annotations, the description transparently states it modifies a copy, operates on JSON animation data only, and lists exclusions to clarify scope.

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?

Three sentences, each serving a clear purpose: action, usage condition, and limitations. Front-loaded with the core action.

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?

Covers purpose, usage condition, and limitations. Lacks specification of return value or confirmation output. Adequate for an experienced user but missing some context.

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%, and the description does not add any additional parameter meaning beyond what is in the schema. Baseline 3.

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?

Description uses specific verb 'Write' and resource 'rotate, translate, and scale timelines for existing bones into a Spine JSON copy'. The negative list distinguishes from sibling tools by explicitly stating what it does not do.

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?

Explicitly says 'Use this when you know exact bone names and keyframes.' Also lists what it does not do, which helps the agent decide not to use it for those tasks.

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