Skip to main content
Glama
Spine Pipeline MCP

Spine Pipeline MCP

by RainLib

skeleton_inspect

Read-only

Inspect a Spine JSON file in the configured read-only root to run basic structural checks, not full validation.

Instructions

Inspect a Spine JSON in the configured read-only root; basic checks, not full validation.

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_inspect"
  }
}

Input Schema

NameRequiredDescriptionDefault
relative_pathYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.1

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so much of the safety profile is covered. The description still adds real context beyond them: it discloses that reads are confined to a "configured read-only root" and that the checks performed are shallow ("basic checks, not full validation"), which sets correct expectations about output depth. It stops short of describing the response shape or what happens if the file is missing.

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 front-loaded sentence: verb, resource, constraint, and scope-limitation in that order, with no filler. Every clause carries distinct information.

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 one-parameter read-only inspection tool this is close to sufficient, and the annotations carry the safety profile. The gap is the absence of an output schema combined with no description of what the inspection returns — an agent cannot tell whether to expect a pass/fail verdict, a list of findings, or parsed structure.

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?

There is one parameter with 0% schema description coverage — the schema only supplies a bare "Relative Path" title. The description partially compensates by indicating that the path is resolved against a "configured read-only root," which clarifies what the path is relative to. It does not specify format, expected extension, or resolution behavior on traversal, so compensation is only partial.

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 pairs the verb "Inspect" with a specific resource (a Spine JSON) and states the scope ("in the configured read-only root"). The clause "basic checks, not full validation" distinguishes it from the validation siblings (skeleton_validate, godot_validate) without naming them, so the differentiation is present but indirect.

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?

"Not full validation" implies that a fuller validation path exists elsewhere and that this tool is the lighter-weight pass, which is useful routing signal. However, it never states when to reach for this versus skeleton_validate, nor any prerequisites or exclusions, so the guidance stays implied rather than explicit.

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