Skip to main content
Glama
TechBot_Blender_MCP

TechBot_Blender_MCP

by bharatnextai

symmetrize_mesh_geometry

Enforce bilateral symmetry on a Blender mesh across a chosen reflection axis and lock midline vertices to prevent seam separation during mirroring.

Instructions

Enforce bilateral symmetry on a designated mesh object across a specified reflection plane (default X), locking sagittal midline vertices to prevent seam separation.

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": "symmetrize_mesh_geometry"
  }
}

Input Schema

NameRequiredDescriptionDefault
viewsNoOptional calibrated reference views for silhouette regression monitoring.
task_idNoOptional task or workflow identifier.
approvedNoDEPRECATED / UNTRUSTED: Client-supplied approval flags in tool arguments are not trusted.
object_nameNoAlias for target_object.
lock_midlineNoWhether to snap and lock midline vertices to exactly 0.0 along the symmetry axis.
symmetry_axisNoReflection plane normal axis (default 'X' for sagittal symmetry).X
target_objectYesName of the target mesh object in the Blender scene.
max_face_countNoUpper face cap limit before rejecting symmetrization.
seam_thresholdNoMidline distance threshold in meters. Midline vertices within this distance are locked strictly to 0 on symmetry axis.
max_vertex_countNoUpper vertex cap limit before rejecting symmetrization.
source_directionNoDirection of symmetry transfer: '+TO_-' mirrors positive coordinates to negative, '-TO_+' reverses, 'AVERAGE' blends both.+TO_-
preserve_topologyNoEnsure vertex, edge, and face counts remain invariant.
rollback_on_failureNoIf true, rollback mesh state bit-for-bit if limits are exceeded or regression occurs.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations at all, the description carries the full burden; it does disclose the key behavior that midline vertices are snapped and locked to prevent seam separation, and 'Enforce' implies mutation. It says nothing about rejection on the vertex/face caps, the bit-for-bit rollback, or topology invariance, which are real behavioral traits of this tool.

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?

A single front-loaded sentence with the core action first and the seam-prevention rationale second. No filler, no repetition of the tool name, nothing to cut.

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 13-parameter mutating mesh operation with no annotations and no output schema, the description covers the central effect but is thin on failure modes and side effects the agent would want to know. The rich schema compensates for parameter detail, so the description is adequate rather than complete.

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 schema already documents all 13 parameters including symmetry_axis, lock_midline, source_direction, and rollback_on_failure. The description only restates 'specified reflection plane (default X)' and midline locking, adding no meaning beyond the schema's own text, so the 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?

States a specific verb and resource ('Enforce bilateral symmetry on a designated mesh object'), plus the scope of the operation (reflection plane, midline locking). No sibling in the catalog performs symmetrization, so the operation is unambiguous even without an explicit contrast sentence.

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 or when-not-to-use guidance: nothing tells the agent when to choose this over edit_mesh, merge_mesh, or optimize_mesh_silhouette, and no prerequisites (existing object, required state) are stated. Only the defaults ('default X') are implied context.

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