Skip to main content
Glama
Spine Pipeline MCP

Spine Pipeline MCP

by RainLib

mesh_replace

Replace mesh UVs, triangles, vertices, or hull (optional edges) while preserving texture; supports continuous Spine 4.3 geometry and explicit bind coordinates for weighted vertices.

Instructions

NEW job: replace uvs/triangles/vertices/hull (optional edges), preserving texture. Continuous geometry only; Spine 4.3; no deform/linked meshes. Weighted vertices need explicit bind coordinates.

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>",
      "skin": "<skin>",
      "slot": "<slot>",
      "attachment": "<attachment>",
      "geometry": "<geometry>"
    },
    "name": "mesh_replace"
  }
}

Input Schema

NameRequiredDescriptionDefault
skinYes
slotYes
job_idYes
geometryYes
attachmentYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.1

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false and destructiveHint=false, and the description adds meaningful preconditions (Spine version, continuous-only geometry, bind coordinates for weighted vertices) plus the texture-preservation guarantee. It does not explain job lifecycle — whether the job is asynchronous, how completion is observed, or what happens to the pre-existing mesh data.

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?

Front-loaded with the operation and target data, then prerequisites, in three terse clauses with no filler. The telegraphic style is dense but every phrase carries constraints; minor cost is that the compressed syntax and parenthetical '(optional edges)' take a moment to parse.

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 five-required-parameter mutation job with a free-form nested geometry object, no output schema, and 0% schema description coverage, the description leaves too much unspecified — the geometry payload shape, the meaning of skin/slot/attachment, and job result handling are all absent.

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 all five parameters are required, yet job_id, skin, slot, and attachment receive no explanation at all. The nested 'geometry' object (additionalProperties: true, no defined shape) is only hinted at via 'uvs/triangles/vertices/hull (optional edges)' and 'bind coordinates', leaving its actual structure and coordinate conventions undocumented.

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 resource: creates a NEW job that replaces mesh UVs, triangles, vertices, and hull (with optional edges), preserving texture. That is far more informative than the bare name 'mesh_replace' and clearly separates it from mesh_inspect, mesh_weights_set, and mesh_policy_validate, though no sibling is named explicitly.

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?

Gives real eligibility conditions rather than a generic 'use this to replace meshes': continuous geometry only, Spine 4.3, no deform or linked meshes, and weighted vertices require explicit bind coordinates. These function as when-not-to-use rules, but no alternative tool is suggested for the excluded cases (e.g., deform/linked meshes).

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