Skip to main content
Glama
Spine Pipeline MCP

Spine Pipeline MCP

by RainLib

godot_validate

Validate Spine assets by loading and sampling them at runtime in an isolated Godot project configured with native Spine support; this checks runtime behavior, not visual approval.

Instructions

Use configured native Spine-enabled Godot in an isolated project. Runtime load/sample, not visual approval.

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

Input Schema

NameRequiredDescriptionDefault
job_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.1

TDQS

C2.9/5.0
Behavior3/5

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

Annotations declare readOnlyHint=false with destructiveHint=false, so the agent already knows this executes something without claiming to destroy data. The description adds real value beyond that by disclosing that execution happens in an isolated project and consists of a runtime load/sample rather than a visual judgement. It omits runtime cost, failure modes, and what a 'sample' produces, which leaves meaningful gaps for a non-read-only tool.

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 very short sentences with no filler, and the mechanism is front-loaded ahead of the exclusion. The density of jargon ("native Spine-enabled Godot") costs a little clarity, but nothing is redundant.

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?

There is no output schema, so the description should convey what validation yields (pass/fail, sampled frames, error output) and how job_id is obtained. Annotations cover only the safety profile. The definition leaves an agent unsure of both required preconditions and the shape of the result.

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% and the single required parameter job_id is effectively undocumented in both schema and description. The description never mentions the job identifier, what a valid job refers to, or whether it must come from a prior staging/export step. For a 1-param tool with no schema help, this is a real gap.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Use configured native Spine-enabled Godot in an isolated project" describes the mechanism (running Godot against a Spine asset) rather than a clean verb+resource; the agent must infer that the tool validates by performing a runtime load/sample. The contrast clause "not visual approval" does narrow the scope meaningfully, but the core action is stated obliquely and packed with unfamiliar jargon.

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?

"Runtime load/sample, not visual approval" is an explicit exclusion that tells the agent when not to reach for this tool. However, no alternative validation sibling (e.g. job_validate, skeleton_validate, mesh_policy_validate) is named as the destination for those excluded cases, so the routing guidance is only half complete.

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