Skip to main content
Glama

recalculate_normals

Fix inverted or inconsistent mesh shading by recalculating normals, with an option to orient them inward when needed.

Instructions

Recalculate mesh normals.

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
nameYes
insideNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.6/5.0
Behavior2/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, yet it says nothing about this being a mutating edit to mesh data, whether the change is reversible, what mode or selection state is required, or how the `inside` flag flips normal direction. Only the bare action is disclosed.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is a single front-loaded sentence with no filler, so there is nothing to trim. However, its brevity comes at the cost of under-specification rather than efficiency, which the other dimensions penalize.

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?

An output schema exists, so return values need not be described, but for a two-parameter mesh mutation with no annotations and zero schema coverage the description is far too thin. It leaves the critical `inside` flag and the mode/target object requirements completely unaddressed.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate for both parameters and does not. The `name` parameter (which mesh) and especially `inside` (default false, meaning normals point inward) are entirely unexplained, leaving the agent with no way to know how to set `inside` correctly.

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 states a specific verb plus resource ("Recalculate mesh normals"), so an agent knows exactly what operation is performed. It does not distinguish this from neighboring mesh-editing siblings such as bevel_mesh or apply_modifier, and it doesn't say which mesh is affected (the required `name` param is what selects it).

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 guidance, no mention of prerequisites such as a selected/active mesh object or object vs. edit mode, and no routing to alternatives. The only implied context is that normals need fixing, which the agent must already know.

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