Skip to main content
Glama
TechBot_Blender_MCP

TechBot_Blender_MCP

by bharatnextai

bake_mesh_surface_map

Bake high-resolution surface detail into normal, displacement, roughness, or AO maps for low-poly meshes, transferring from a source mesh or self-baking with UV and color-space setup.

Instructions

Bake high-resolution mesh surface detail (tangent normal maps, displacement heightmaps, roughness, AO) from a detailed source mesh to a low-poly target retopology mesh, or self-bake detail onto the target mesh. Handles Cycles bake setup, UV verification/auto-unwrapping, non-color space, ray distance/cage extrusion, and image export.

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

Input Schema

NameRequiredDescriptionDefault
widthNoBaked image texture width in pixels.
heightNoBaked image texture height in pixels.
marginNoMargin in pixels around UV islands during baking.
task_idNoOptional task or workflow identifier.
approvedNoDEPRECATED / UNTRUSTED: Client-supplied approval flags in tool arguments are not trusted.
map_typeNoSurface map type to bake.NORMAL
color_spaceNoColor space setting for the baked image datablock (default 'Non-Color' for normal/displacement/roughness).Non-Color
object_nameNoAlias for target_object.
save_filepathNoOptional absolute file path on disk to save the baked image (PNG).
source_objectNoName of the high-poly source mesh object containing detailed sculpting/features. If omitted or equal to target_object, performs self-bake.
target_objectYesName of the target low-poly (retopology) mesh object to receive the bake.
cage_extrusionNoRay casting cage extrusion distance in meters for selected-to-active bake.
max_ray_distanceNoMaximum ray casting distance in meters (0.0 = unlimited/auto).
rollback_on_failureNoRestore scene render engine, material, and object selection state if baking fails.
auto_unwrap_if_neededNoIf target mesh has no UV layer, automatically unwrap with Smart UV Project before baking.
use_selected_to_activeNoWhether to bake detail from source_object to target_object. Automatically False if source_object is omitted or identical to target_object.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.4/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It does disclose meaningful behavior — Cycles bake setup, automatic UV unwrapping, ray-distance/cage extrusion, and image export — which tells the agent the scene (render engine, materials, UVs) will be mutated. It stops short of saying what is left changed after the call, whether the unwrap persists, or what is returned.

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?

Two sentences, front-loaded with the action and output artifacts, then a compact capability list. The enumerated 'Handles ...' sentence is somewhat feature-dump-like but each item corresponds to real behavior an agent should anticipate.

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 16-parameter mutation tool with no annotations and no output schema, the description covers the workflow but is silent on results (returned image path or datablock, behavior when save_filepath is omitted) and on post-bake scene state. Adequate to select the tool, thin for invoking it confidently.

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 is already self-documenting; baseline is 3. The description reinforces the source/target relationship and the self-bake condition, but the map-type list merely echoes the enum and no extra syntax or default guidance is added.

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 names a specific verb+resource ('Bake ... mesh surface detail') and enumerates the concrete outputs (tangent normal, displacement, roughness, AO). It also distinguishes two modes — high-poly source to low-poly target, or self-bake — but does not differentiate itself from nearby siblings such as bake_texture, bake_object_texture, or bake_materials.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage context is implied rather than stated: the retopology workflow (high-poly detail onto a low-poly target) and the 'or self-bake' case hint at when each mode applies. There is no explicit when-to-use/when-not-to-use statement and no named alternative among the sibling bake tools.

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