Skip to main content
Glama
Spine Pipeline MCP

Spine Pipeline MCP

by RainLib

mesh_policy_validate

Read-only

Validates mesh attachment policies against skin, slot, and region rules to catch vertex, influence, and bone constraint violations before export.

Instructions

Check {rules:[{skin,slot,attachment,continuous?,max_vertices?,max_influences?,regions?}]}. Regions use vertices plus allowed_bones/rigid_bone/forbidden_ancestors. Static 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>",
      "policy": "<policy>"
    },
    "name": "mesh_policy_validate"
  }
}

Input Schema

NameRequiredDescriptionDefault
job_idYes
policyYes

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?

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description contributes the "Static only" scope limit, which is real behavioral information, but it says nothing about what a check produces (violations list? pass/fail?), whether it fails fast, or how errors are surfaced — notable given there is 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.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short fragments with no filler and the payload shape front-loaded, so nothing is wasted. The dense pseudo-JSON notation, however, is hard to parse as prose and pushes readability onto the agent rather than the description.

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?

This is a validation tool with a nested object parameter, zero schema description coverage, and no output schema — the description should therefore explain the validation outcome and the meaning of the policy fields. It supplies only the field skeleton and an unexplained "Static only" constraint, leaving an agent unable to predict what a call returns or how to interpret results.

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?

Schema coverage is 0% and the policy parameter is a bare object with additionalProperties=true, so the description carries the full burden — and it does document the rules array fields (skin, slot, attachment, continuous, max_vertices, max_influences, regions) plus the region fields. That is genuine value beyond the schema, but the notation is terse with no meaning, types, or defaults for optional fields, and job_id is never mentioned.

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?

"Check {rules:[...]}" indicates a validation operation over a policy structure, and the name plus payload shape make the resource (mesh skinning policy rules) inferable. However, "Check" is a weak verb, the description never states plainly that it validates a policy against a job, and it gives no cue distinguishing it from siblings like mesh_inspect or godot_validate.

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?

"Static only" is the sole usage constraint and it is ambiguous — presumably meaning non-animated meshes are in scope, but that is left to inference. There is no statement of when to call this versus mesh_weights_get/set or the other *_validate siblings, and no prerequisites or ordering guidance.

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