Skip to main content
Glama
Sign In
Blender MCP Ultra

Blender MCP Ultra

by 3bdull4h2008
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

set_studio_world

Set the world background strength and RGB color for a studio environment in Blender, adjusting brightness from subtle to bright.

Instructions

Set world background for studio environment.

Args: strength: Background strength (0.1 = subtle, 1.0 = bright). color: RGB background color.

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

Input Schema

NameRequiredDescriptionDefault
colorNo
strengthNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv3.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, the description must disclose the mutation and its side effects, but it only restates that the world background is set. It does not say whether this replaces the existing background, affects sky texture, or 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?

The description is compact and front-loaded, with no filler or repeated schema content. It earns its length for a two-parameter tool, though the brevity comes at the cost of missing behavioral context.

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 simple two-parameter setter it is minimally sufficient: the operation and both parameters are named. It is not complete because the color array format is ambiguous, there are no annotations, and it does not clarify the effect on an existing world or sky setup.

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?

The description adds a helpful strength range (0.1 subtle, 1.0 bright) and labels color as RGB, which the schema does not provide. It does not specify the exact array length or color value format, so it only partially compensates for the 0% schema coverage.

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 (set) and resource (world background) and adds studio context, so an agent can tell what it acts on. It does not explicitly distinguish itself from siblings such as setup_world_sky_texture, but the resource is clear enough for a 4.

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 call this instead of a sibling such as setup_world_sky_texture or setup_studio_lighting, and no exclusions or prerequisites. 'For studio environment' implies one context but does not explain trade-offs.

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