Skip to main content
Glama
TechBot_Blender_MCP

TechBot_Blender_MCP

by bharatnextai

create_light

Add and position point, sun, spot, or area lights in the active Blender scene with configurable energy, color, size, shadows, and transform settings.

Instructions

Create and position a light source in the active scene (Point, Sun, Spot, Area) with configurable energy, color, and transform.

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

Input Schema

NameRequiredDescriptionDefault
nameYesUnique name for the 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).
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.POINT
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

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description must carry the full behavioral burden. It identifies a scene mutation but omits important details such as approval requirements, reversibility, active-scene prerequisites, and side effects, despite the schema containing an untrusted approval flag.

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 a single front-loaded sentence with no unnecessary wording. It efficiently conveys the core action, target, light types, and main configurable dimensions.

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?

This is a complex 18-parameter mutation tool with no annotations and no output schema. The schema covers parameter details, but the description is too sparse for the behavioral context an agent needs, including approval mechanism, undo semantics, and relationship to configure_light.

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 schema already documents all 18 parameters in detail. The description mentions energy, color, and transform at a high level but adds no syntax, conditional usage, or constraints beyond what the schema provides.

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 states a specific verb and resource: create a light source in the active scene. It also names the supported light types and configurable aspects, making the operation clear. It does not explicitly distinguish itself from the sibling configure_light, so it falls short of a 5.

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 explicit when-to-use guidance or comparison with alternatives such as configure_light. The description implies creating a new light, but does not say when to choose this tool versus modifying an existing one, nor does it state exclusions or prerequisites.

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