Skip to main content
Glama
Spine Pipeline MCP

Spine Pipeline MCP

by RainLib

animation_copy

Copies an existing Spine animation to a new name in a new staging job and rejects name collisions.

Instructions

Copy an existing animation to a new name in a NEW staging job; refuses name collisions.

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>",
      "source": "<source>",
      "target": "<target>"
    },
    "name": "animation_copy"
  }
}

Input Schema

NameRequiredDescriptionDefault
job_idYes
sourceYes
targetYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.1

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare mutation (readOnlyHint=false) with destructiveHint=false, so the bar is lower, yet the description still adds real value: the copy creates a new staging job as a side effect and name collisions are rejected rather than overwritten. It does not say what is returned (new animation id / new job id) or whether the source is left untouched.

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?

A single compact sentence with the scope and collision behavior front-loaded and no filler; nothing could be cut without losing content.

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 3-parameter mutation tool with no output schema and no parameter documentation in the schema, the definition is thin: it never explains job_id, never says what the copy returns, and its 'new job' wording sits uneasily with a required job_id. The collision-refusal detail is the one piece of real completeness.

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?

Schema description coverage is 0%, so the description must carry all parameter meaning. It maps loosely onto source (existing animation) and target (new name), but leaves job_id completely undefined, and the claim that the result goes into a NEW job actively muddies what job_id is for.

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 and resource ('Copy an existing animation') plus the destination scope ('a new name in a NEW staging job'), which distinguishes it from sibling copy/stage tools like stage_json_copy. It is clear what the tool produces, though it does not name an alternative by name.

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?

'in a NEW staging job' implies a constraint (you cannot copy into an existing job) and 'refuses name collisions' implies a failure condition, so usage is implied but never stated as explicit when-to-use vs when-not guidance or with a named alternative.

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