Skip to main content
Glama
Spine Pipeline MCP

Spine Pipeline MCP

by RainLib

bone_keys_set

Replace a single rotate, translate, or scale timeline in a new Spine job using linear or stepped keys, including value-based rotation for Spine 4.3.

Instructions

Replace one rotate/translate/scale timeline in a NEW job. Spine 4.3 rotate uses value. Linear/stepped only.

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": {
      "job_id": "<job_id>",
      "animation": "<animation>",
      "bone": "<bone>",
      "timeline": "<timeline>",
      "keys": "<keys>"
    },
    "name": "bone_keys_set"
  }
}

Input Schema

NameRequiredDescriptionDefault
boneYes
keysYes
job_idYes
timelineYes
animationYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.1

TDQS

C2.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false and openWorldHint=false; the description adds real behavioral limits beyond that: only linear/stepped interpolation is supported and Spine 4.3 rotate keys use a 'value' field. However, the terse 'Spine 4.3 rotate uses value' phrase is cryptic, and nothing explains what 'NEW job' means operationally (does a job need to be created first, can it fail if the job is reused, is the replacement atomic).

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is short and front-loads the core action, which is good, but the second and third fragments are telegraphic to the point of ambiguity ('Spine 4.3 rotate uses value') and the space saved buys no clarity. Efficient but under-specified rather than genuinely concise.

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

Completeness2/5

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

A five-parameter mutation with no output schema, no schema descriptions, and only a one-line description leaves too much unspecified: acceptable timeline values, key object fields, what the response/job reference looks like, and error behavior for unsupported interpolation. Complete enough only to recognize the tool's domain, not to call it reliably.

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

Parameters2/5

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

All five parameters (job_id, animation, bone, timeline, keys) are required with 0% schema description coverage, so the description carries the full burden and largely fails: it hints at timeline values (rotate/translate/scale) and at a 'value' field inside keys, but never explains bone naming, animation strings, key object shape, or the job_id contract. An agent would be guessing at the structure of the keys array.

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?

States a specific verb ('Replace'), a specific resource ('one rotate/translate/scale timeline'), and a scope ('in a NEW job'), which meaningfully separates it from siblings like animation_copy or animation_retime that operate on existing animations. The name/description pairing is coherent for a bone-key writer, though the phrasing is terse enough that an agent must infer 'bone_keys_set' == setting keyframes for one channel.

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?

The only usage signal is the parenthetical constraint 'in a NEW job', which implies the target job must be new/fresh but never says how to obtain it or whether job_validate should run first. There is no explicit statement of when to prefer this over animation_copy/animation_retime, and no exclusion of unsupported cases beyond the interpolation note.

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