Skip to main content
Glama
Spine Pipeline MCP

Spine Pipeline MCP

by RainLib

job_validate

Read-only

Run static structural checks against a staged job to detect issues without changing it. Confirm the job structure before continuing.

Instructions

Run static structural checks against a staged job, without changing it.

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

Input Schema

NameRequiredDescriptionDefault
job_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.1

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, and the phrase "without changing it" is consistent with them rather than contradictory. The one piece of genuinely additive information is "static", telling the agent the job is inspected rather than executed. However, it says nothing about how failures surface (raised error vs. report contents), which matters for a validation tool with no output schema.

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?

A single front-loaded sentence with no filler, and the non-mutating guarantee is placed where it is read first. It is efficient, though the brevity leaves the result semantics unaddressed.

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 validation tool the agent's key question is what it gets back or what happens on failure, and there is no output schema to answer that. Combined with an entirely undocumented sole parameter and no stated preconditions beyond "staged", the definition leaves too much to inference for the tool's job.

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% – job_id is documented only as a bare string titled "Job Id". The description adds only the loose constraint that the job must be "staged"; it gives no format, example, or indication of where a staged job id comes from, so it does not compensate for the coverage 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?

States a specific verb and object ("Run static structural checks") against a clearly named resource ("a staged job"), which separates it from the mesh/skeleton/godot validation siblings by resource. It stops short of explicitly contrasting itself with those siblings, so a 4 rather than a 5.

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 phrase "staged job" – the reader infers this runs after staging and before any commit/apply step. There is no explicit when-to-use, no when-not-to-use, and no named alternative (e.g. a runtime validation tool), so guidance remains inferred rather than stated.

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