Skip to main content
Glama

blender_lighting

Create and manage all light types, HDRI environments, and professional lighting rigs in Blender. Includes sun, point, spot, area lights, three-point setups, and light adjustments.

Instructions

PORTMANTEAU PATTERN RATIONALE: Consolidates 7 related lighting operations into single interface. Prevents tool explosion while maintaining full lighting workflow from basic lights to professional HDRI setups. Follows FastMCP 2.14.3 best practices.

Professional lighting system for Blender supporting all light types, HDRI environments, and lighting rigs.

Light Creation (4 operations):

  • create_sun: Generate directional sunlight with shadow control for outdoor scenes

  • create_point: Create omnidirectional point light for general illumination

  • create_spot: Generate focused spotlight with beam angle and softness control

  • create_area: Create rectangular area light for soft, realistic shadows

Lighting Setups (2 operations):

  • setup_three_point: Create professional three-point lighting rig (key, fill, rim lights)

  • setup_hdri: Configure HDRI environment lighting with world background

Light Management (1 operation):

  • adjust_light: Modify properties of existing lights (energy, color, position, etc.)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
operationNoThe lighting operation to perform. Must be one of: "create_sun", "create_point", "create_spot", "create_area", "setup_three_point", "setup_hdri", "adjust_light". - Light creation: "create_*" operations (use: light_name, location, rotation, energy, color + type-specific params) - Lighting setups: "setup_*" operations (use: minimal parameters, auto-position lights) - Light adjustment: "adjust_light" (use: light_name + properties to modify)create_sun
light_nameNoName for the new light object. Default: "Light". Must be unique in scene. Required for: all "create_*" and "adjust_light" operations.Light
light_typeNoType of light for creation operations. One of: "SUN", "POINT", "SPOT", "AREA". Default: "SUN". Auto-detected from operation when possible.SUN
locationNo3D position coordinates (x, y, z) in world space. Default: (5, 5, 5). Used for: all "create_*" operations.
rotationNoRotation angles in degrees (x, y, z) around each axis. Default: (0, 0, 0). Primarily affects: "create_spot" for beam direction.
energyNoLight intensity/energy multiplier. Default: 1.0. Range: 0.0 to 100.0. Higher values = brighter light. Used for: all light creation and adjustment.
colorNoLight color as RGB values. Default: (1, 1, 1) (white). Range: 0.0 to 1.0 per channel. Used for: all light creation and adjustment.
shadow_soft_sizeNoShadow softness for sun lights. Default: 0.1. Range: 0.0 to 10.0. Higher values = softer shadows. Only used for: "create_sun".
sizeNoPhysical size of area lights. Default: 1.0. Range: 0.01 to 100.0. Larger sizes = softer, more realistic shadows. Only used for: "create_area".
spot_sizeNoBeam angle in degrees for spot lights. Default: 45.0. Range: 1.0 to 180.0. Smaller angles = more focused beam. Only used for: "create_spot".
spot_blendNoEdge softness for spot lights. Default: 0.15. Range: 0.0 to 1.0. Higher values = softer beam edges. Only used for: "create_spot".

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

No annotations are provided, so the description carries full burden. It describes the side effects of each operation (e.g., creates a light object, modifies existing light, auto-positions for setups). However, it could disclose more about constraints (e.g., unique name requirement, scene prerequisites) or potential errors. The description is adequate but not exhaustive.

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 well-structured with categories and bullet points, making key information scannable. The portmanteau rationale front-loads context. However, the rationale paragraph is somewhat verbose for an agent; it could be more concise without losing clarity.

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?

Given the tool's complexity (11 parameters, 7 operations), the description covers all operations and parameter mappings thoroughly. It does not explain return values, but an output schema exists (per context signals). The description is complete enough for an agent to understand and invoke the tool correctly.

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 100%, but the description adds significant value beyond the schema. It explicitly maps parameters to operations (e.g., 'shadow_soft_size Only used for: create_sun'), provides ranges, defaults, and contextual usage notes. This helps the agent select correct parameters per operation, exceeding the baseline.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states it is a 'Professional lighting system for Blender supporting all light types, HDRI environments, and lighting rigs.' It enumerates specific operations (create_sun, create_point, etc.) grouped into categories, making the tool's scope unambiguous. The tool is distinct from siblings like blender_camera or blender_materials.

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?

The description provides a rationale for the portmanteau pattern and explains when to use each operation (e.g., 'Light creation: create_* operations (use: light_name, location, rotation, energy, color + type-specific params)'). It gives clear context for operation selection but does not explicitly state when not to use the tool or which sibling tools serve as alternatives.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/sandraschi/blender-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server