Skip to main content
Glama
Spine Pipeline MCP

Spine Pipeline MCP

by RainLib

mesh_weights_get

Read-only

Retrieves up to 256 staged mesh vertices with named bones, bone-local bind coordinates, and weights for a given skin, slot, and attachment.

Instructions

Read up to 256 vertices with named bones, bone-local bind coordinates and weights from a staged mesh.

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

Input Schema

NameRequiredDescriptionDefault
skinYes
slotYes
limitNo
job_idYes
offsetNo
attachmentYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.1

TDQS

B3/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 adds real value beyond that by disclosing the result payload (named bones, bone-local bind coordinates, weights) and a 256-vertex cap, but it does not explain pagination behavior, what happens when limit exceeds 256, or failure modes.

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 well-formed sentence with the scope and the 256 cap front-loaded and no wasted clauses. It is efficient, though the brevity is partly why parameter coverage is thin.

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?

With no output schema, the description usefully summarizes what comes back, which is the biggest gap it could have filled. However, for a six-parameter tool with four required identifiers and zero schema documentation, an agent still cannot tell what skin, slot, or attachment mean or how paging works.

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% across six parameters, so the description must carry the burden and largely does not. 'Staged mesh' loosely maps to job_id and 'up to 256' maps to limit, but skin, slot, attachment, and offset are given no meaning, and no guidance on how limit/offset interact is provided.

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 description states a specific verb ('Read') and a precisely scoped resource: vertices with named bones, bone-local bind coordinates, and weights, taken from a staged mesh. That is enough to distinguish it from mesh_weights_set (the write counterpart) without naming it, though it never explicitly contrasts with any sibling.

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?

There is no explicit when-to-use or when-not-to-use guidance and no named alternative. The only implicit context is 'from a staged mesh', which hints at a prerequisite staging step but does not state it as a condition for calling the tool.

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