Skip to main content
Glama
Spine Pipeline MCP

Spine Pipeline MCP

by RainLib

spine_export

Runs a licensed Spine CLI export on a staged copy to generate project, JSON, atlas, and PNG files without publishing.

Instructions

Run explicitly configured licensed Spine CLI on another copy; produce project/JSON/atlas/PNG. Staging 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>"
    },
    "name": "spine_export"
  }
}

Input Schema

NameRequiredDescriptionDefault
job_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.1

TDQS

C2.7/5.0
Behavior3/5

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

Beyond the annotations, the description discloses the licensed/configured Spine CLI requirement, the staging-only scope, and the produced artifact types. It leaves important behavior unspecified, such as what 'another copy' means, whether outputs overwrite anything, and how job_id is used, but the safety annotations already reduce the burden.

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 with no filler and the action is front-loaded. The semicolon-separated artifact list is efficient, though the terseness contributes to ambiguity elsewhere.

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 one-parameter export tool with no output schema, the definition names output artifact types but omits the meaning of job_id, the source of 'another copy,' and what the caller receives or should expect on completion. It is not complete enough to invoke confidently without guessing.

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

Parameters1/5

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

The single required job_id parameter has no description in the schema (0% coverage), and the tool description never explains what a job id represents or where it comes from. The description therefore adds no semantic meaning for the only input.

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 gives a specific action ('Run ... Spine CLI') and concrete output artifacts (project/JSON/atlas/PNG), so the tool's function is recognizable. It does not explicitly contrast with sibling export/staging tools, and 'another copy' is vague, so it falls short of full sibling differentiation.

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?

'Staging only' is a useful scope constraint, but the description never says when to choose this over stage_asset_bundle, stage_json_copy, or other staging tools. There are no prerequisites beyond the licensed CLI and no when-not guidance.

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