Skip to main content
Glama
Spine Pipeline MCP

Spine Pipeline MCP

by RainLib

mesh_weights_set

Replaces existing mesh vertex bindings' weights, normalizes and sorts them, and retains bind x/y for Spine 4.3 mesh weight updates.

Instructions

NEW job: updates=[{vertex:0,weights:{bone:1}}]. Replace existing bindings' weights, normalize/sort; retain bind x/y. Spine 4.3 only; no deform/linked meshes. Does not preserve pose.

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>",
      "updates": "<updates>"
    },
    "name": "mesh_weights_set"
  }
}

Input Schema

NameRequiredDescriptionDefault
skinYes
slotYes
job_idYes
updatesYes
attachmentYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.1

TDQS

C2.6/5.0
Behavior1/5

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

The annotations declare destructiveHint=false, yet the description says it "Replace[s] existing bindings' weights" and "Does not preserve pose" – both plainly destructive to existing weight data and the current pose. That is a direct conflict with the supplied annotation, even though the description itself is unusually candid about the side effects.

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?

It is dense and free of filler, but it opens with a cryptic "NEW job:" and an example payload instead of a plain statement of purpose, so the reader must decode the intent before the constraints. The information-to-word ratio is high, but the ordering is not front-loaded around what the tool does.

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 tool with no output schema and no annotation coverage of value, the description leaves too much open: the role of job_id, skin, slot and attachment is unstated, and it does not say what is returned on creating the job. It covers the tricky updates payload and the Spine/deform restrictions well but falls short overall.

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% for five required parameters, and the description only clarifies one of them via the example payload updates=[{vertex:0,weights:{bone:1}}]. The meanings and expected formats of skin, slot, job_id and attachment are left undocumented in both schema and prose.

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?

The phrase "Replace existing bindings' weights, normalize/sort" gives a specific verb and resource, so an agent knows this writes vertex/bone weights rather than reading them. It never names the read counterpart mesh_weights_get or any other sibling, so differentiation relies on the name and the get/set convention rather than on the text.

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?

It states hard preconditions: "Spine 4.3 only; no deform/linked meshes", which is real when-to-use context and effectively a when-not for those targets. There is no explicit routing to an alternative when you have a newer Spine version or linked meshes, so the guidance is implied rather than complete.

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