Skip to main content
Glama
TechBot_Blender_MCP

TechBot_Blender_MCP

by bharatnextai

configure_render_settings

Set Blender render engine, resolution, frame range, FPS, output format/path, and active camera to prepare scene renders or align output settings.

Instructions

Configure active render settings: render engine ('BLENDER_EEVEE_NEXT', 'CYCLES', 'BLENDER_WORKBENCH'), resolution dimensions, percentage, frame range, FPS, output image format, output path, and active camera.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "configure_render_settings"
  }
}

Input Schema

NameRequiredDescriptionDefault
fpsNoFrames per second (1 to 240).
lookNoColor management look contrast preset.
gammaNoColor management display gamma adjustment (-32.0 to 32.0, default 1.0).
cyclesNoCycles engine configuration bundle.
engineNoRender engine: 'BLENDER_EEVEE_NEXT', 'CYCLES', or 'BLENDER_WORKBENCH'.
qualityNoImage quality percentage (1 to 100) for lossy formats like JPEG and WEBP.
task_idNoOptional task or workflow identifier.
approvedNoDEPRECATED / UNTRUSTED: Client-supplied approval flags in tool arguments are not trusted as proof of human consent.
denoiserNoDenoising algorithm for Cycles ('OPENIMAGEDENOISE' or 'OPTIX').
exposureNoColor management exposure adjustment in EV (-32.0 to 32.0).
fps_baseNoFramerate base divisor (e.g., 1.001 for 23.976 fps).
frame_endNoAnimation timeline end frame.
color_modeNoImage color mode ('BW', 'RGB', 'RGBA'). Compatibility depends on output_format.
time_limitNoRender time limit in seconds for Cycles engine (0.0 = unlimited).
color_depthNoBit depth per channel ('8', '16', '32'). Supported depths depend on output_format.
compressionNoImage compression level percentage (0 to 100) for formats like PNG and OPEN_EXR.
frame_startNoAnimation timeline start frame.
max_bouncesNoTotal maximum light bounces for Cycles render (0 to 1024).
output_pathNoConfigured render output filepath or directory (e.g. '//render/' or absolute path).
resolution_xNoRender resolution width in pixels (1 to 65536).
resolution_yNoRender resolution height in pixels (1 to 65536).
active_cameraNoName of camera object in scene to designate as active camera.
cycles_deviceNoDevice type for Cycles rendering ('CPU' or 'GPU').
frame_currentNoAnimation timeline current frame or playhead position to evaluate.
output_formatNoOutput image file format ('PNG', 'JPEG', 'OPEN_EXR', 'TARGA', 'TIFF').
use_denoisingNoEnable denoising for Cycles render engine.
cycles_samplesNoRender sample count for Cycles engine.
glossy_bouncesNoMaximum glossy/specular light bounces for Cycles render (0 to 1024).
view_transformNoColor management view transform preset.
volume_bouncesNoMaximum volume light bounces for Cycles render (0 to 1024).
diffuse_bouncesNoMaximum diffuse light bounces for Cycles render (0 to 1024).
color_managementNoColor management settings bundle.
film_transparentNoWhether to render background transparent with alpha channel.
adaptive_thresholdNoNoise threshold for Cycles adaptive sampling (0.0 to 1.0).
adaptive_min_samplesNoMinimum samples before adaptive sampling begins for Cycles (0 to 65536).
transmission_bouncesNoMaximum transmission light bounces for Cycles render (0 to 1024).
resolution_percentageNoRender resolution scaling percentage (1 to 1000).
use_adaptive_samplingNoEnable adaptive sampling for Cycles render engine.
transparent_max_bouncesNoMaximum transparent light bounces for Cycles render (0 to 1024).

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 burden, yet it discloses nothing about side effects: whether changes persist to the .blend file, whether switching engines invalidates engine-specific values, whether this is a partial or full overwrite, or what is returned. 'Configure' implies mutation but the consequences are opaque.

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 front-loaded sentence with no filler, but its enumerated list largely restates the schema property names rather than adding meaning, so it is efficient without being especially informative.

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?

For a 39-parameter mutation tool with nested objects and no annotations or output schema, the description is far too thin: it omits default behavior, the relationship between the flat Cycles/color keys and the nested bundles, and any statement of effect on the scene. The schema covers individual fields but not the tool's overall contract.

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% and each of the 39 parameters is individually documented with ranges and enums, so the baseline is 3. The description adds only a coarse grouping of settable categories, without explaining engine-dependent applicability or how the flat keys interact with the nested 'cycles' and 'color_management' bundles.

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 ('Configure') plus a specific resource ('active render settings') and enumerates the domains covered (engine, resolution, frame range, FPS, format, path, camera). An agent can tell this is a settings-mutation tool, though the description never distinguishes it from siblings like render_scene or configure_camera.

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 description only lists what can be set; it offers no guidance on when to use this versus render_scene, no note that it does not trigger a render, and no conditions for choosing between the EEVEE/CYCLES/WORKBENCH paths. Usage must be entirely inferred.

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