Skip to main content
Glama
TechBot_Blender_MCP

TechBot_Blender_MCP

by bharatnextai

configure_world

Configures the active Blender world background, including color, emission strength, node-tree activation, physical sky models, and environment image rotation for scene lighting.

Instructions

Configure the active world background settings (color, strength, and node-tree activation).

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_world"
  }
}

Input Schema

NameRequiredDescriptionDefault
colorNoRGB background color components [r, g, b] normalized to 0.0-1.0.
task_idNoOptional task or workflow identifier for grouping related scene mutation operations.
altitudeNoObserver altitude above sea level in meters [0.0 to 100000.0] (Nishita). Default 100.0.
approvedNoDEPRECATED / UNTRUSTED: Client-supplied approval flags in tool arguments are not trusted as proof of human consent. Mutations must be approved through a trusted approval mechanism.
sky_typeNoOptional physical sky model type: 'MULTIPLE_SCATTERING' (Nishita Multiple Scattering), 'SINGLE_SCATTERING', 'PREETHAM', 'HOSEK_WILKIE', or 'NISHITA' (alias for MULTIPLE_SCATTERING).
strengthNoBackground emission strength multiplier (>= 0.0).
sun_discNoWhether to render the visible sun disc in the physical sky (Nishita).
sun_sizeNoAngular diameter of the sun disc in radians [0.0 to 1.5708] (Nishita). Default ~0.009512 rad (0.545 deg).
turbidityNoAtmospheric turbidity [1.0 to 10.0] for Preetham/Hosek-Wilkie models. Default 2.2.
use_nodesNoWhether the world shader uses an active node tree.
air_densityNoAir molecule density multiplier (Rayleigh scattering) [0.0 to 1000.0] (Nishita). Default 1.0.
sun_rotationNoSolar azimuth rotation angle in radians [-6.2832 to 6.2832] (Nishita). Default 0.0.
ground_albedoNoGround albedo reflection factor [0.0 to 1.0] for Preetham/Hosek-Wilkie models. Default 0.3.
ozone_densityNoOzone layer density multiplier (Ozone absorption) [0.0 to 1000.0] (Nishita). Default 1.0.
sun_elevationNoSolar elevation angle above the horizon in radians [-1.5708 to 1.5708] (Nishita). Default ~0.2618 rad (15 deg).
sun_intensityNoMultiplier for the sun disc brightness (>= 0.0, default 1.0) (Nishita).
aerosol_densityNoAerosol / haze / dust particle density multiplier (Mie scattering) [0.0 to 1000.0] (Nishita). Default 1.0.
environment_imageNoOptional image datablock name or absolute filepath to bind to an environment texture background node.
environment_rotationNoRotation for the environment texture (HDRI) or background mapping. Either a single float (rotation angle around Z-axis in radians) or a 3-element list [rx, ry, rz] in radians.

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 behavioral burden, yet it discloses nothing about mutation semantics: whether changes are reversible, which of the 19 properties are overwritten versus left untouched, or that mutations require a trusted approval mechanism (only visible obliquely in the schema's deprecated 'approved' field). For a 19-parameter scene mutation, this 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?

A single front-loaded sentence with no filler. It is slightly misleading in implying the tool only touches color, strength, and node trees, but it is efficient and readable.

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 19-parameter, zero-required, unannotated mutation tool with no output schema, the description is far too thin — it never explains the interaction between use_nodes and the physical sky parameters, nor the approval/trust model. The rich schema compensates partially, but the description does not prepare an agent to call this correctly.

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 the physical-sky parameters, ranges, and defaults are already fully documented in the schema. The description adds nothing beyond naming three of the nineteen parameters, which is the baseline case of schema doing 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 description names a specific verb and resource ("Configure the active world background settings") and lists three concrete facets (color, strength, node-tree activation), which distinguishes it from siblings like configure_light or configure_render_settings. It stops short of explicitly routing against alternatives, but the world-background scope is unambiguous.

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 alternatives, no prerequisites, and no note about the approval requirement hinted at by the deprecated 'approved' parameter. An agent must infer everything about invocation context from the schema alone.

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