Skip to main content
Glama
Spine Pipeline MCP

Spine Pipeline MCP

by RainLib

animation_retime

Divides animation timing by a positive speed factor to create a retimed copy in a new job; supports linear/stepped curves and rejects Bezier.

Instructions

Return a new job with animation times divided by positive speed. Only linear/stepped; rejects Bezier.

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>",
      "speed": "<speed>"
    },
    "name": "animation_retime"
  }
}

Input Schema

NameRequiredDescriptionDefault
speedYes
job_idYes
animationYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.1

TDQS

A3.6/5.0
Behavior4/5

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

Annotations declare readOnlyHint=false with destructiveHint=false, so the safety profile is already known; the description usefully confirms it by stating the result is a NEW job, i.e. the original is preserved rather than mutated in place. It also discloses two real behavioral traits the annotations do not cover: the input validation rule (speed must be positive) and a hard failure mode (Bezier curves are rejected). It stops short of describing the error shape or what the returned job contains.

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 short sentences, front-loaded with the result ('Return a new job') before the constraints. Nothing is padded, though the phrase 'Only linear/stepped' is compressed to the point of being slightly cryptic about what exactly is linear or stepped.

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 three-parameter mutation tool with no output schema, the description does state that a new job is returned, which covers the return side. It remains incomplete on job_id semantics, on what happens to the source job explicitly, and on where this sits relative to the copy/export siblings.

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 coverage is 0% with three required parameters and no field descriptions, so the description must carry meaning. It adds the crucial constraint that speed must be a positive divisor and that the animation must be linear or stepped, which compensates for two of the three fields. job_id is left entirely unexplained — nothing says whether it identifies the source job whose animation is being retimed.

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 a specific operation on a specific resource: producing a new job whose animation times are scaled by a speed divisor. That is more precise than the bare name 'animation_retime', though it never distinguishes itself from a sibling such as animation_copy, which plausibly also produces a derived job.

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?

'Only linear/stepped; rejects Bezier' functions as a when-not condition, telling the agent which animations this tool cannot handle. However, there is no statement of when to choose this tool over animation_copy or the other job-oriented siblings, so the routing guidance is only implied.

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