Skip to main content
Glama

set_world_background

Set a Blender scene’s world background to a solid color or HDRI environment, lighting the scene and giving metals and glass reflections. Choose one source and adjust strength or rotation.

Instructions

Set the world background to a solid colour or an HDRI environment.

An HDRI lights the whole scene and gives metal and glass something to reflect; without one, metals look dull. Give exactly one of color, hdri_path or builtin_hdri.

Args: color: RGB colour [r, g, b] for a plain background. hdri_path: Absolute path to an HDRI image (.hdr, .exr, ...). builtin_hdri: One of the HDRIs that ship with Blender: city, courtyard, forest, interior, night, studio, sunrise, sunset. strength: Background strength, 0 to 1000, default 1.0. rotation: HDRI turn around the vertical axis in radians, to move where the light comes from. -6.283 to 6.283.

Returns: Confirmation dict.

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": "set_world_background"
  }
}

Input Schema

NameRequiredDescriptionDefault
colorNo
rotationNo
strengthNo
hdri_pathNo
builtin_hdriNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv3.0.0
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / builtin_hdri
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "enum": [
      +    "city",
      +    "courtyard",
      +    "forest",
      +    "interior",
      +    "night",
      +    "studio",
      +    "sunrise",
      +    "sunset"
      +  ],
      +  "title": "Builtin Hdri"
      +}
    • addedInput schema / properties / rotation
      Added value: +{
      +  "default": 0,
      +  "title": "Rotation",
      +  "type": "number"
      +}
  2. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

No annotations exist, so the description carries the burden, and it does real work: the exactly-one-of-three argument constraint, numeric bounds (strength 0–1000, rotation ±6.283 radians) that the schema does not declare, and the physical effect of an HDRI on metal/glass. It does not say whether the existing world is replaced or a new world is created, nor whether the change is reversible.

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?

Front-loaded purpose, then a one-sentence rationale, then the exclusivity rule, then a clean Args block — easy to scan. The trailing 'Returns: Confirmation dict' is largely redundant given an output schema exists and is the one line that doesn't earn its place.

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

Completeness4/5

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

For a five-parameter mutation tool with no annotations and no schema-level parameter docs, the definition covers arguments, ranges, exclusivity and the lighting consequence well. The remaining gap is state semantics — whether the current world settings are overwritten or appended, and how it relates to set_world_sky.

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% (titles only, no bounds), yet the description documents all five parameters with type, format and meaning: RGB triple for color, absolute path plus acceptable extensions for hdri_path, the built-in options, the strength range with default 1.0, and rotation units in radians plus why to use it. This fully compensates for the schema gap.

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 first sentence names a specific verb and resource ('Set the world background') and immediately disambiguates the two operating modes: solid colour vs HDRI environment. It never references the sibling tool set_world_sky, which is the nearest alternative an agent could confuse it with, so it stops short of full sibling differentiation.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Strong usage context: it explains when to prefer an HDRI ('lights the whole scene and gives metal and glass something to reflect; without one, metals look dull') and states the mutual-exclusion rule 'Give exactly one of color, hdri_path or builtin_hdri'. It gives no explicit exclusion pointing to set_world_sky or guidance about when NOT to touch the world at all.

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