Skip to main content
Glama
TechBot_Blender_MCP

TechBot_Blender_MCP

by bharatnextai

align_normals

Recalculates or flips Blender mesh face normals to fix outside, inside, or inverted orientation, verifying winding consistency and topology before applying changes.

Instructions

Recalculate or flip mesh face normals (outside, inside, or flip) with winding consistency and topology verification.

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

Input Schema

NameRequiredDescriptionDefault
nameYesName of the target mesh object in the active scene.
facesNoFaces to operate on: 'all', 'selected', or an explicit list of non-negative integer face indices.all
actionNoNormal operation: RECALCULATE_OUTSIDE, RECALCULATE_INSIDE, or FLIP.RECALCULATE_OUTSIDE
task_idNoOptional task or workflow identifier.
approvedNoDEPRECATED / UNTRUSTED: Client-supplied approval flags in tool arguments are not trusted as proof of human consent.
object_nameNoAlias for name.
target_objectNoAlias for name.
expected_snapshot_idNoBase-mesh snapshot fingerprint. Required when faces is an explicit index list.

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 burden; it does add meaningful behavior beyond a restatement by disclosing winding consistency and topology verification. However, it never states that this mutates the mesh in place, whether it is reversible, or how permissions/snapshot requirements apply — all material for a geometry-write tool with 8 parameters.

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?

One front-loaded sentence with no filler; the operation is stated first and the modes follow. The nested parenthetical makes it slightly dense but nothing is redundant.

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 mutation tool with no annotations, no output schema, and eight parameters, the description covers the what and the modes but omits in-place/reversibility behavior and the snapshot precondition implied by 'expected_snapshot_id'. It is minimally 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 eight parameters, making 3 the baseline. The description's mode list ('outside, inside, or flip') only loosely parallels the schema enum and adds nothing about 'faces', the snapshot requirement for explicit index lists, or the alias parameters.

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 gives a specific verb and resource ('Recalculate or flip mesh face normals') and enumerates the three modes (outside, inside, flip), so an agent knows exactly what operation it performs. It does not, however, differentiate itself from the sibling 'recalculate_normals', whose name suggests overlapping behavior.

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 statement of when to use this tool versus the sibling 'recalculate_normals', nor any prerequisites, exclusions, or conditions. The parenthetical mode list hints at use cases but gives no routing guidance.

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