Skip to main content
Glama
TechBot_Blender_MCP

TechBot_Blender_MCP

by bharatnextai

configure_anatomical_mask

Configures anatomical region masks or vertex groups on a Blender mesh using spatial falloff and optional bilateral symmetry, so you can isolate features like horns or wings for targeted editing.

Instructions

Configure an anatomical region mask / vertex group on a designated mesh object (e.g. Horns, Wings, Scales) with smooth spatial weight falloff and optional bilateral symmetry.

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": {
      "target_object": "<target_object>",
      "mask_name": "<mask_name>"
    },
    "name": "configure_anatomical_mask"
  }
}

Input Schema

NameRequiredDescriptionDefault
radiiNoOptional [rx, ry, rz] radii for ellipsoidal region bounds.
actionNoAction to perform: 'SET' assigns weights, 'ADD' sums with existing, 'SUBTRACT' subtracts, 'CLEAR' zeroes group.SET
centerNoCenter coordinate [x, y, z] for spherical, cylindrical, or bounding regions.
radiusNoRadius in meters for SPHERE or CYLINDER region types.
falloffNoWeight falloff curve from region center to outer boundary.SMOOTH
task_idNoOptional task or workflow identifier.
approvedNoDEPRECATED / UNTRUSTED: Client-supplied approval flags in tool arguments are not trusted.
mask_nameYesName of the anatomical vertex group / mask (e.g. 'Horns', 'Wings', 'Body_Scales', 'Spine_Ridges').
max_weightNoMaximum peak weight at region center.
min_weightNoMinimum weight outside or at region perimeter.
object_nameNoAlias for target_object.
region_typeNoSpatial or geometric region formula used to evaluate vertex membership weights.SPHERE
normal_vectorNoDirection vector [x, y, z] for NORMAL_FACING region type (e.g. [0, 0, 1] for dorsal).
region_boundsNoOptional bounding box [xmin, ymin, zmin, xmax, ymax, zmax] for BOUNDING_BOX region type.
symmetry_axisNoIf specified (e.g. 'X'), evaluates and mirrors mask weights symmetrically across the plane.NONE
target_objectYesName of the target mesh object in the Blender scene.
normal_toleranceNoAlignment tolerance for NORMAL_FACING (dot product threshold = 1.0 - normal_tolerance).
rollback_on_failureNoIf true, rolls back vertex group modifications on error.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.1/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full behavioral burden. It does disclose two meaningful traits beyond the schema surface: smooth spatial weight falloff and optional bilateral mirroring across a plane. However, it omits that this is a mutation of persisted vertex-group data, whether new groups are created, and safety behavior such as the rollback_on_failure and deprecated approved parameters that the schema hints at.

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 verb, resource, and target stated first, then qualifiers. The parenthetical object examples add utility rather than noise, though the phrase 'smooth spatial weight falloff' is slightly redundant with the schema's falloff enum.

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 an 18-parameter mutation tool with no annotations and no output schema, one sentence is not enough. It never explains the conditional coupling between region_type and center/radius/region_bounds/normal_vector, nor the target_object vs object_name alias, nor what happens to existing weights under SET versus ADD versus SUBTRACT versus CLEAR.

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% across all 18 parameters, so the structured schema already explains region_type, falloff, symmetry_axis, and the deprecated approved flag. The description adds only loose framing ('smooth spatial weight falloff', 'bilateral symmetry') that maps onto falloff and symmetry_axis without adding new meaning, which is the baseline-3 case for high coverage.

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?

Names a specific verb ("Configure") and resource ("anatomical region mask / vertex group on a designated mesh object"), plus concrete examples (Horns, Wings, Scales) that make the domain tangible. It does not name or contrast with the sibling inspect_anatomical_mask, so an agent must infer read-vs-write separation on its own.

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?

No when-to-use, when-not, or prerequisite guidance appears anywhere in the description. It never says whether the mask must already exist, whether this replaces or merges with prior weights, or how it relates to inspect_anatomical_mask or configure_semantic_landmarks.

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