Skip to main content
Glama
TechBot_Blender_MCP

TechBot_Blender_MCP

by bharatnextai

configure_light

Update an existing Blender light's type, energy, color, transform, shadow, spot, or area settings in the active scene to adjust scene lighting.

Instructions

Configure properties and transform of an existing light source in the active scene (Point, Sun, Spot, Area). Updates energy, color, location, rotation, spot size/blend, and area size.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

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

Input Schema

NameRequiredDescriptionDefault
nameYesUnique name of the existing light object.
sizeNoSize or radius for AREA and POINT lights in meters.
colorNoRGB light color components [r, g, b] normalized to 0.0-1.0.
shapeNoShape for AREA lights: 'SQUARE', 'RECTANGLE', 'DISK', or 'ELLIPSE'.SQUARE
energyNoLight power/energy in Watts (for Sun, typical values are 1-10). Must be non-negative.
size_yNoSecondary Y dimension in meters for RECTANGLE and ELLIPSE AREA lights (>= 0.0).
task_idNoOptional task or workflow identifier for grouping related scene mutation operations.
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.
locationNo3D world location coordinates [x, y, z].
spot_sizeNoCone angle in radians for SPOT lights (0.0 to 3.1416).
light_typeNoType of light source: POINT, SUN, SPOT, or AREA.
spot_blendNoSoft edge blend factor for SPOT lights (0.0 to 1.0).
use_shadowNoWhether this light casts shadows in render calculations.
volume_factorNoVolume scattering contribution factor multiplier (>= 0.0).
diffuse_factorNoDiffuse reflection contribution factor multiplier (>= 0.0).
rotation_eulerNoEuler rotation angles in radians [rx, ry, rz].
specular_factorNoSpecular reflection contribution factor multiplier (>= 0.0).
shadow_soft_sizeNoLight size for shadow softness radius in meters (>= 0.0).
shadow_buffer_clip_startNoNear clipping distance for shadow buffer evaluation in meters (>= 0.0001).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.2/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 for a mutation tool, and it leaves the critical question unanswered: with 18 of 19 parameters optional, are unspecified properties preserved or reset to defaults? It also omits permissions, reversibility/undo behavior, and what happens if the named light is absent, adding nothing beyond the safety hints already spelled out in the schema (such as the deprecated 'approved' flag).

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?

Two sentences, front-loaded with purpose and scope before the field enumeration. Slightly redundant field listing, but it aids quick scanning and there is no filler.

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 19-parameter mutation tool with no annotations and no output schema, the definition covers what it changes but not the semantics an agent most needs: whether this is a partial or full update, and failure behavior for a bad name. The rich schema compensates for parameter-level detail, which keeps this from being lower.

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 every parameter already has units, ranges, enums, and type-specific applicability documented in the schema. The description's second sentence merely re-lists a subset of those fields (energy, color, location, rotation, spot size/blend, area size) without adding syntax, defaults, or interaction rules, so baseline 3 applies.

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 gives a specific verb ('Configure') and resource ('existing light source in the active scene') and names the four light types it covers. The word 'existing' distinguishes it from create_light, so an agent can tell the two apart, though the sibling is never named explicitly.

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?

Usage is only implied: 'existing light source' suggests this mutates rather than creates, which contrasts softly with create_light. There is no explicit statement of when to prefer this over alternatives, no note that the light must already exist in the active scene, and no mention of failure when the name doesn't match.

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