Skip to main content
Glama
Spine Pipeline MCP

Spine Pipeline MCP

by RainLib

mesh_inspect

Read-only

Inspect a Spine asset's skins, meshes, topology, continuity, and weights from exactly one source path or job ID to validate static mesh structure.

Instructions

Inventory skins/meshes, topology, continuity and weights. Supply exactly one source path or job ID. Static only.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "mesh_inspect"
  }
}

Input Schema

NameRequiredDescriptionDefault
job_idNo
relative_pathNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.1

TDQS

A3.8/5.0
Behavior3/5

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

The read-only, non-destructive, closed-world annotations already establish the safety profile, and the description is consistent with them. The static-only limitation and inventory facets add scope beyond those annotations, but result granularity, job-based behavior, and failure cases are not disclosed.

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?

Three short sentences front-load the purpose, then state the input constraint and scope limit without filler. The wording is dense but efficient and appropriate for a two-parameter tool.

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?

The definition is sufficient for a basic static, read-only inspection call and covers the crucial source-selection rule that the schema misses. With no output schema, however, the absence of any result-shape detail, source-resolution semantics, or sibling differentiation leaves noticeable gaps.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 0% schema description coverage, the description does important work by identifying the two inputs as alternative source selectors and imposing an exactly-one constraint absent from the schema. It still leaves the path's base or root and the origin or format of an accepted job ID unexplained.

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?

"Inventory" plus "skins/meshes, topology, continuity and weights" gives a concrete operation, resource, and set of inspection facets, while "Static only" bounds the asset scope. It does not explicitly distinguish this overview from the mesh weight, validation, or replacement siblings, so it is clear rather than fully differentiating.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

"Supply exactly one source path or job ID" provides a concrete invocation requirement, and "Static only" excludes use outside static inspection. There is no alternative for non-static assets or guidance on when to choose a path versus a job ID, so the routing guidance is useful but incomplete.

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