Skip to main content
Glama
TechBot_Blender_MCP

TechBot_Blender_MCP

by bharatnextai

bake_materials

Bakes materials, lighting, normals, roughness, or ambient occlusion into an image texture for a target mesh using Cycles, with optional PNG saving to disk.

Instructions

Bake materials, lighting, normals, roughness, or ambient occlusion into an image texture for a target mesh object using Cycles rendering engine. Supports saving to disk.

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

Input Schema

NameRequiredDescriptionDefault
widthNoBake image width in pixels (64 to 8192).
heightNoBake image height in pixels (64 to 8192).
marginNoPixel margin around baked UV islands (0 to 64).
task_idNoOptional task or workflow identifier.
approvedNoDEPRECATED / UNTRUSTED: Client-supplied approval flags in tool arguments are not trusted as proof of human consent.
bake_typeNoType of bake pass to perform.COMBINED
image_nameNoTarget image datablock name. Created if not already existing.
object_nameYesName of the target mesh object with valid UV coordinates.
save_filepathNoOptional file path to write the baked PNG image to disk.
use_selected_to_activeNoWhether to bake from selected objects to the active object.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/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 disclosure burden, yet it covers only the basic action. It does not say whether an existing image datablock is overwritten, whether render settings/engine are mutated, how long a bake may run, or what happens when the target object lacks UVs — all material for a GPU-heavy mutating operation. 'Supports saving to disk' is the only behavioral nuance and it is thin.

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 tight sentences with the core operation front-loaded and the disk-save capability trailing. No filler, though the tool would benefit from one more sentence of routing guidance rather than more adjectives.

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 10-parameter, GPU-intensive bake operation with no annotations and no output schema, the description stops short of what an agent needs: the return value (image datablock name? filepath? status?) is unstated, and the deprecated 'approved' flag and 'use_selected_to_active' semantics are left entirely to the schema. Adequate but with clear gaps.

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 each of the 10 parameters is already documented in the schema, including bake_type enum values, resolution bounds, margin, and save_filepath. The description adds nothing parameter-specific beyond naming the bake pass types, which the enum already provides; 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 concrete verb and resource: bake named pass types (materials, lighting, normals, roughness, AO) into an image texture for a target mesh via Cycles. The purpose is unambiguous, but there is no differentiation from close siblings like bake_texture, bake_object_texture, or bake_mesh_surface_map, so an agent cannot tell which bake tool to pick from the description alone.

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 guidance on when to use this tool versus the several other bake_* siblings, nor any stated prerequisites beyond the passing mention that Cycles is involved. It never says whether the scene must already be configured for Cycles, whether the object must be active or selected, or when saving to disk should be requested versus skipped.

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