Skip to main content
Glama
TechBot_Blender_MCP

TechBot_Blender_MCP

by bharatnextai

inspect_anatomical_mask

Inspect anatomical mask or vertex group distributions on a Blender mesh and evaluate bilateral symmetry, including asymmetry RMSE, midline seam vertices, and symmetry pairings.

Instructions

Inspect anatomical mask / vertex group distributions and evaluate bilateral mesh symmetry (asymmetry RMSE, midline seam vertices, symmetry pairing).

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

Input Schema

NameRequiredDescriptionDefault
mask_nameNoOptional name of specific mask / vertex group to inspect (if omitted, lists all groups).
object_nameNoAlias for target_object.
symmetry_axisNoAxis to evaluate bilateral symmetry across (default 'X' for sagittal symmetry).X
target_objectYesName of the target mesh object in the Blender scene.
seam_thresholdNoMidline distance threshold in meters for classifying sagittal seam vertices.
evaluate_symmetryNoWhether to calculate bilateral pairing and asymmetry RMSE.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description carries the full disclosure burden; it does establish the tool as a read-only inspection that computes symmetry metrics, which is meaningful behavioral context. However it omits cost/performance implications (full-mesh bilateral pairing can be expensive), whether results are cached, and what happens when evaluate_symmetry is false — gaps that matter for a 6-parameter geometry tool.

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 primary purpose first and the secondary symmetry metrics in a parenthetical. No filler or repetition, though the slash-separated dual purpose makes it slightly denser than ideal.

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?

For a 6-parameter tool with no annotations and no output schema, the description should say what comes back — whether the distributions are counts, weights, or per-vertex lists, and the shape of the symmetry report. It names the metrics but leaves the return contract entirely unspecified.

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%, so the baseline is 3; the schema already explains target_object, symmetry_axis, seam_threshold and evaluate_symmetry. The description adds only the framing that these produce 'distributions' and 'midline seam vertices', which lightly reinforces seam_threshold and symmetry_axis but goes no further than the schema.

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?

States a specific verb ('Inspect') with two concrete resources (mask/vertex group distributions, bilateral mesh symmetry) and even names the computed metrics (asymmetry RMSE, seam vertices, pairing). It implicitly contrasts with configure_anatomical_mask via the inspect/configure split, but never states that differentiation explicitly.

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 guidance on when to use this versus configure_anatomical_mask or the other inspect_* tools, and no prerequisites stated (e.g. must the object already have a mask, must it be applied to a mesh). The only usage hint is that omitting mask_name lists all groups, which is a parameter behavior rather than a usage rule.

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