Skip to main content
Glama

set_world

Destructive

Control a Blender scene's background and ambient light with a color, preset, HDRI, or strength; optionally make the render background transparent.

Instructions

Set the background and ambient light: a plain colour or an HDRI image. color is '#rrggbb' or [r, g, b] (0-1). An explicit color wins over the preset colour. strength multiplies the light (1 is normal). With neither colour, preset nor hdri only the strength changes. hdri lights the scene with an image and gives metal and glass something to reflect. It is a path to an .hdr or .exr file, or the name of a studio light shipped with Blender: city, courtyard, forest, interior, night, studio, sunrise, sunset (the answer lists them in builtin_hdris; an unknown name gives the list in the error). rotation_deg turns it about Z. visible_to_camera=false keeps the HDRI for light and reflections, and the camera sees the plain color or preset colour instead (without them: the colour the world had). Works in eevee and cycles. A later call without hdri and with a colour or preset makes the world a plain colour again. transparent=true makes the render background transparent (alpha 0) and the world only lights the scene. The flag stays on until set_world is called again with transparent=false.

Input Schema

NameRequiredDescriptionDefault
hdriNo
colorNo
presetNo
strengthNo
transparentNo
rotation_degNo
visible_to_cameraNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A4.4/5.0
Behavior5/5

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

Annotations only declare destructiveHint=true, readOnlyHint=false, and openWorldHint=false. The description adds substantial behavioral context: color/preset precedence, strength multiplication, HDRI builtin names and error behavior, rotation about Z, visible_to_camera masking, transparent flag stickiness, and engine compatibility.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is dense but front-loaded and every sentence carries specific operational meaning. It specifies scope first, then precedence, persistence, parameter behavior, and engine support without filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 7-parameter, zero-schema-description mutation tool with no output schema, the description supplies nearly all missing behavioral and parameter context. It covers core semantics, persistence rules, and compatibility; return values need not be explained because no output schema exists.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must carry parameter meaning. It defines color format and precedence, strength behavior, HDRI path and builtin names, rotation semantics, transparent alpha behavior, and visible_to_camera effects; only individual preset meanings are left largely to the schema enum values.

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 and resource: set the world background and ambient light. It clearly scopes the world/environment, though it does not explicitly distinguish itself from lighting siblings such as add_light or setup_lighting.

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?

The use case is implied by the purpose: setting background and ambient light. However, there is no explicit when-to-use vs alternatives guidance or exclusions, so the agent must infer that this is the world-level lighting tool rather than a per-light tool.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.