Skip to main content
Glama
TechBot_Blender_MCP

TechBot_Blender_MCP

by bharatnextai

recalculate_normals

Recalculate or flip mesh face normals to correct shading and winding issues, choosing outside, inside, or flipped orientation with topology verification.

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": "recalculate_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 supplied, the description carries the full burden, and it does add real behavioral context: it states that winding consistency is enforced and topology is verified, implying a mutating operation with validation. It omits whether the mesh is modified in place, whether the change is reversible, and what happens when topology verification fails.

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 well-formed sentence with the core verb front-loaded and no filler. The parenthetical list of modes partly duplicates the action enum in the schema, which is minor redundancy.

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 an eight-parameter mutating tool with no annotations and no output schema, the description is adequate on purpose but silent on mutation safety, the snapshot prerequisite for explicit face lists, and any indication of what a successful call reports back.

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 every parameter including the enum action, the faces selector, and expected_snapshot_id is already documented in the schema. The description merely restates the enum values and adds no semantics beyond what the schema provides, which is the expected baseline.

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 pair (recalculate/flip) and resource (mesh face normals), and enumerates the three modes of operation. It stops short of differentiating itself from the sibling align_normals, which an agent could reasonably confuse with normal recalculation.

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?

The parenthetical modes hint at the operations but give no guidance on when to choose RECALCULATE_OUTSIDE versus FLIP, no prerequisites, and no mention of the related align_normals sibling. An agent must infer all routing decisions.

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