Skip to main content
Glama
TechBot_Blender_MCP

TechBot_Blender_MCP

by bharatnextai

bake_object_texture

Bake material, lighting, normal, roughness, or ambient occlusion passes into an image texture for a mesh using Cycles, with optional PNG export 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_object_texture"
  }
}

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?

With no annotations supplied, the description carries the whole burden and covers little: it names the Cycles engine and that results can be saved to disk, but says nothing about whether this is a long-running render, what side effects occur (image datablock creation, render settings changes), or whether it requires an active object or GPU. For a potentially expensive render/bake mutation, that is a substantial gap.

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 verb and resource, with no filler. The trailing 'Supports saving to disk' is slightly redundant with the save_filepath parameter but is short enough not to be wasteful.

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 tool with no annotations and no output schema, the description should say what comes back (image name? file path? confirmation?) and whether the operation is destructive or slow. It covers the core action but leaves these operational questions open.

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 coverage is 100%, so every parameter is already documented, and the description adds only marginal meaning by restating the bake-pass categories that map to the bake_type enum. Baseline 3 applies since the schema does the heavy lifting.

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 verb 'bake' plus the resource 'image texture for a target mesh object' is specific, and the enumerated bake passes (materials, lighting, normals, roughness, AO) tell an agent exactly what class of operation this is. It does not, however, distinguish itself from siblings named bake_texture, bake_materials, or bake_mesh_surface_map, which appear to overlap.

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 other bake_* siblings, no prerequisites (e.g., valid UVs, an active object), and no exclusions. The only usage hint is implicit in the word 'target mesh object'.

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