blend-ai

by HoldMyBeer-gg

Overview Schema Source Related Servers Discussions Admin

Python

Local

create_light

Add a new point, sun, spot, or area light to a Blender scene, with optional name, location, energy, and color.

Instructions

Create a new light in the scene.

Args: type: Light type. One of: POINT, SUN, SPOT, AREA. name: Optional name for the light. location: XYZ location as [x, y, z], default [0, 0, 0]. energy: Light energy/power, default 1000. color: RGB color as [r, g, b], default [1.0, 1.0, 1.0].

Returns: Confirmation dict with light name and properties.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`name`	No
`type`	Yes
`color`	No
`energy`	No
`location`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv1.7.0Sep 28, 2026
- addedInput schema / additionalProperties
```
Added value: +false
```
- addedInput schema / properties / type / enum
```
Added value: +[
+  "AREA",
+  "POINT",
+  "SPOT",
+  "SUN"
+]
```
First observedv0.1.0Mar 22, 2026

TDQS

B3.3/5.0

Behavior3/5

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

No annotations are supplied, so the description carries the full disclosure burden. It does state the return shape ('Confirmation dict with light name and properties'), which helps, but it never says which scene or collection the light lands in, whether it becomes selected/active, or what permissions are needed for a mutation.

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 one-line purpose followed by a compact Args/Returns block; each line carries information. Slightly more boilerplate than necessary, but nothing wasted.

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?

An output schema exists, so the Returns line is redundant rather than filling a gap. For a mutation tool with no annotations and no output-schema-based side-effect info, the description should say more about where the light is created and its default state, so it is adequate but incomplete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description is the only source of parameter meaning — and it delivers: it enumerates all five parameters, the enum values for type, and the defaults for name, location, energy, and color. Minor gap is that it doesn't specify the length/format constraints on color and location beyond 'as [x, y, z]'.

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?

States a specific verb and resource ('Create a new light in the scene'), which is unambiguous and distinct from the many read/delete siblings. It does not, however, distinguish itself from the closely related create_light_rig, so an agent gets no explicit help choosing between the two.

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?

No when-to-use guidance, no prerequisites, and no mention of the sibling create_light_rig as an alternative. The agent must infer the context entirely.

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

Deploy Server