Skip to main content
Glama
Spine Pipeline MCP

Spine Pipeline MCP

by RainLib

stage_json_copy

Copies a Spine JSON into a new isolated staging job so you can work on it without altering the source file.

Instructions

Copy one Spine JSON into a new isolated staging job. Never changes the source.

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": {
      "relative_path": "<relative_path>"
    },
    "name": "stage_json_copy"
  }
}

Input Schema

NameRequiredDescriptionDefault
relative_pathYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.1

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false and destructiveHint=false, so the agent knows this is a non-destructive write. The description adds genuinely useful context beyond that: the output lands in a new isolated staging job and the source file is never modified. However, it omits what happens on name collisions, whether repeated calls create multiple jobs, and what identifies the resulting job.

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?

Two short sentences, with the action and its destination front-loaded and the source-safety guarantee immediately following. There is no filler; the brevity is appropriate for a single-parameter tool.

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?

For a mutation tool with no output schema, the description should cover the parameter's meaning and the effect of the call. It states the effect partially (new isolated job, source untouched) but leaves 'relative_path' undefined and gives no hint of what the caller receives back, so an agent could still miscalculate inputs or mis-handle the result.

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

Parameters5/5

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

This definition has only one parameter and 0% schema description coverage. The description must carry the full burden of explaining that parameter, but 'relative_path' is never defined: it doesn't say what the path is relative to, whether it points to an existing Spine JSON file, or what format is expected. With one undocumented parameter and no compensating text, this is a clear gap.

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 verb and resource ('Copy one Spine JSON') plus a concrete destination ('new isolated staging job'), which is far more informative than the bare name stage_json_copy. It doesn't explicitly distinguish itself from sibling copy/export tools like animation_copy or stage_asset_bundle, but the Spine-JSON-to-staging-job scope is clear enough to select on.

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?

There is no when-to-use guidance: nothing says when to stage a JSON copy versus exporting (spine_export) or bundling assets (stage_asset_bundle), nor what preconditions must hold. The only contextual cue is the implicit safety note 'Never changes the source', which is behavior, not usage routing.

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