Skip to main content
Glama
Spine Pipeline MCP

Spine Pipeline MCP

by RainLib

skeleton_validate

Read-only

Statically check bone references, mesh topology and weights, and timeline times in a Spine skeleton file to catch errors before export. Does not guarantee visual correctness.

Instructions

Statically check bone references, mesh topology/weights and timeline times. Not a visual guarantee.

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": "skeleton_validate"
  }
}

Input Schema

NameRequiredDescriptionDefault
relative_pathYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.1

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already establish that the tool is read-only, non-destructive, and closed-world. The description adds that checking is static and that a pass should not be treated as visual confirmation, which is useful behavioral context, but it does not explain result format, failure behavior, or asset requirements.

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?

The description is two compact sentences with the primary purpose stated first and the important limitation second. Every phrase contributes useful information without repetition.

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 validator with one required parameter, no output schema, and no schema descriptions, the description is too thin. It covers the checks performed and the visual limitation, but leaves the parameter meaning and expected results unspecified, which leaves an agent with gaps before invocation.

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?

The input schema provides a relative_path parameter with 0% description coverage, and the description does not mention the parameter at all. It therefore adds no meaning about what the path is relative to or what kind of target file is expected.

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 states a specific verb ('Statically check') and concrete resources: bone references, mesh topology/weights, and timeline times. It is clear what the tool validates, but it does not name or distinguish itself from sibling validators such as godot_validate, job_validate, or mesh_policy_validate.

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?

Usage is implied by the validation purpose and the caveat that it is not a visual guarantee. However, the description does not say when to use this instead of the other validate tools, nor does it state prerequisites or exclusions.

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