Skip to main content
Glama
TechBot_Blender_MCP

TechBot_Blender_MCP

by bharatnextai

bind_armature_mesh

Binds a target mesh to an armature using an ARMATURE modifier and vertex groups; choose automatic, envelope, name-only, or manual weighting to skin characters or props.

Instructions

Binds a target mesh to an armature via ARMATURE modifier and vertex groups (AUTOMATIC, ENVELOPE, NAME_ONLY, MANUAL).

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": {
      "mesh_object_name": "<mesh_object_name>",
      "armature_name": "<armature_name>"
    },
    "name": "bind_armature_mesh"
  }
}

Input Schema

NameRequiredDescriptionDefault
task_idNoOptional task or workflow identifier.
approvedNoDEPRECATED / UNTRUSTED: Client-supplied approval flags in tool arguments are not trusted as proof of human consent.
bind_modeNoBinding method: AUTOMATIC (heat weighting), ENVELOPE, NAME_ONLY (vertex groups only), MANUAL (explicit weights).AUTOMATIC
armature_nameYesName of the source armature object.
vertex_weightsNoOptional dictionary of bone vertex weights: {bone_name: {vertex_index: weight}}.
use_deform_onlyNoWhether to create vertex groups only for bones with use_deform=True (defaults to True).
mesh_object_nameYesName of the target mesh object to skin.
expected_snapshot_idNoOptimistic concurrency state hash of the armature.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full burden. It discloses the underlying mechanism (modifier + vertex groups), which is useful, but says nothing about the mutation's consequences — whether existing vertex groups or weights are overwritten, whether bone envelopes/heat weighting can fail on non-manifold or zero-area geometry, or what happens when vertex_weights and MANUAL conflict.

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 front-loaded sentence with the action first and the mechanism second — no filler. Minor waste in re-listing the four enum values that the schema already defines.

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?

This is a mutating, multi-parameter tool (8 params, nested weights object, an optimistic-concurrency snapshot, and a deprecated untrusted approval flag) with no annotations and no output schema. The description does not cover overwrite/undo semantics, snapshot mismatch behavior, or what the tool returns on success, leaving significant gaps for an agent to call it safely.

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

Parameters3/5

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

Schema description coverage is 100% and every parameter, including the enum modes, the nested vertex_weights dictionary, and expected_snapshot_id, is already documented in the schema. The description's parenthetical mode list merely repeats the enum values, adding no new meaning; baseline 3 applies.

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 names a specific verb ("Binds") and both resources (target mesh, armature), plus the mechanism (ARMATURE modifier and vertex groups), which clearly separates it from siblings like create_armature or edit_armature_bones. It does not explicitly contrast itself with any named sibling, so it falls short of a 5.

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 when-to-use guidance: no prerequisites (e.g., armature must already exist or be in rest pose), no statement of when to prefer this over manual weighting or a sibling tool, and no guidance on which of the four bind modes to pick in a given situation. The mode list is enumerated but unexplained in decision terms.

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

Deploy Server

Other Tools