Skip to main content
Glama

rig_creature

Rigs a clean organic creature mesh with bone chains and smooth skin weights so physics or scripts can bend tentacles, tails, wings, or spines; exports GLB/FBX without animation clips.

Instructions

Soft rig for an organic creature (tentacles, tails, vines, rays, fish): bone chains with smooth skin weights, so engine scripts or physics (Verlet, springs) can bend it. No animation clips are made.

Call it on a clean mesh: run retopologize_mesh first (generated meshes are about 300k faces with stray shells; a quad retopology of 5k to 20k faces skins and deforms far better). input_mesh: a GLB. preset: "chain": one chain of bones (default 8) along the mesh's main axis, or axis; for tentacles, tails, vines. Bones are named _01.. from the root (name default "tentacle"). "spine": the same along the body, named spine_01.. (default 6 bones). "wings": stingray, manta, bat or bird: a spine along the body length (bones, default 6) and, on each side, wing_chains (default 3) chains of wing_bones (default 4) fanning from the body to the wing edge. Named spine_01.., wing_L1_01.. and the mirrored wing_R1_01.. (L is the positive side of the left-right axis: +X when that is X, the creature's left when it faces -Y as generated meshes do; chain 1 is nearest the head). "auto" (default): chain if long and thin, wings if flat and broad, else spine; the report says which and why. axis: "x", "y", "z" or [x, y, z]: the chain direction, or the body length for "wings" (default: from the mesh's principal axes; for wings, the left-right axis is the one the mesh is mirror symmetric across). root_end: which end the chain (or the spine, at the head) starts from: "min" or "max" along the axis, or a point [x, y, z] (the end nearest it). Default: a vertical chain starts at its lower end, otherwise at the thicker end (a tentacle's base); wings start at the wider end (a tail is narrow). weights: "auto" tries Blender's heat weights and falls back to a smooth distance falloff from the bones when they fail (more than 1% of the vertices unweighted or on a far bone, common on generated meshes); "distance" always uses the falloff. Every vertex gets at most 4 influences, normalised. Bone axes: local Y runs along each bone; rotate about local X to bend (for wings, local Z is the surface normal, so local X rotation flaps up and down). Output: <output_dir or the input's folder>/rig.glb and .fbx (armature and skinned mesh, rest pose). Returns the bones (head, tail, parent), the preset used, weight coverage and method, and warnings. Headless Blender on the CPU, a few seconds.

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": {
      "input_mesh": "<input_mesh>"
    },
    "name": "rig_creature"
  }
}

Input Schema

NameRequiredDescriptionDefault
axisNo
nameNo
bonesNo
presetNoauto
weightsNoauto
root_endNo
input_meshYes
output_dirNo
wing_bonesNo
wing_chainsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A5/5.0
Behavior5/5

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

With no annotations, the description carries the full behavioral burden and does so: it discloses that no animation clips are made, how weights are chosen and when the heat-weight method falls back, the 4-influence normalization, output file formats and locations, and the headless CPU runtime. It also states what the return payload contains: bones, preset, weight coverage and method, and warnings.

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?

Despite its length, the description is front-loaded with purpose and prerequisite, then organized by parameter in a scannable way; the detail is warranted by 10 undocumented parameters. The wing-axis and bone-axis notes are dense but directly actionable, and no sentence is mere filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 10-parameter, annotation-free, output-schema-free rigging tool, the description covers prerequisites, parameter behavior, output artifacts, return values, runtime, and failure fallbacks. An agent has enough information to decide when to call it and how to interpret the result without opening other documentation.

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

Parameters5/5

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

Schema description coverage is 0%, so the description must define all 10 parameters, and it does: input_mesh as a GLB, preset values with defaults and naming schemes, axis forms, root_end options, weights modes, bone counts, wing chain and bone counts, and output_dir behavior. It adds substantial meaning beyond the bare schema titles and defaults.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: 'Soft rig for an organic creature...' and immediately scopes it with 'No animation clips are made,' distinguishing it from animation or mesh-generation siblings. It also names the required prerequisite retopologize_mesh, so an agent can place it correctly in a pipeline.

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

Usage Guidelines5/5

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

Explicitly says to call it on a clean mesh and to run retopologize_mesh first, with concrete reasons: generated meshes are about 300k faces with stray shells, while a 5k-20k quad retopology skins and deforms better. It also explains when the 'auto' preset chooses chain, wings, or spine, giving explicit when-to-use guidance rather than leaving it implied.

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