Skip to main content
Glama
HoldMyBeer-gg

blend-ai

by HoldMyBeer-gg
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

set_eevee_light_path

Adjust EEVEE direct and indirect light intensity multipliers in Blender 5.1+ to control how strongly lighting contributes. Only applies when using EEVEE render engine.

Instructions

Set EEVEE light intensity controls (Blender 5.1+).

Scales how strongly direct and indirect lighting contribute. Only applies when the render engine is EEVEE.

Args: direct_intensity: Multiplier for light arriving straight from a lamp. Range 0.0-10.0, 1.0 is unchanged. Leave unset to keep the current value. indirect_intensity: Multiplier for bounced light. Range 0.0-10.0, 1.0 is unchanged. Leave unset to keep the current value.

Returns: Dict with both intensities after the change.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
direct_intensityNo
indirect_intensityNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv1.7.0
    • removedInput schema / properties / diffuse_intensity
      Removed value: -{
-  "anyOf": [
-    {
-      "type": "number"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "default": null,
-  "title": "Diffuse Intensity"
-}
    • addedInput schema / properties / direct_intensity
      Added value: +{
+  "anyOf": [
+    {
+      "type": "number"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Direct Intensity"
+}
    • removedInput schema / properties / glossy_intensity
      Removed value: -{
-  "anyOf": [
-    {
-      "type": "number"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "default": null,
-  "title": "Glossy Intensity"
-}
    • addedInput schema / properties / indirect_intensity
      Added value: +{
+  "anyOf": [
+    {
+      "type": "number"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Indirect Intensity"
+}
    • removedInput schema / properties / transmission_intensity
      Removed value: -{
-  "anyOf": [
-    {
-      "type": "number"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "default": null,
-  "title": "Transmission Intensity"
-}
  2. Addedv1.2.2

TDQS

A4/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and largely meets it: it discloses the 0.0-10.0 range, that 1.0 means unchanged, that unset parameters preserve the current value, and that the return contains both intensities. It omits whether the change is undoable or requires an active scene/object, so not quite a 5.

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 purpose and the EEVEE-only constraint are front-loaded in the first two lines, and the Args block is tight. The Returns section is mildly redundant given an output schema exists, costing a small amount of efficiency.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-parameter optional mutation with no annotations, the description supplies ranges, defaults, neutral values, and the engine precondition, and an output schema covers return shape. Only the side effects on the scene (undo, object targets) are left unstated.

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 0%, yet the description fully compensates: it explains what each multiplier means (direct light vs bounced light), the valid range, the neutral value of 1.0, and the null/unset behavior. That is more than the schema communicates.

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 ('Set EEVEE light intensity controls') and scopes it to Blender 5.1+ and the EEVEE render engine, which meaningfully narrows it against the many sibling light/rendering tools. It does not, however, name a sibling (e.g. set_light_property) to disambiguate overlap, 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 Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The precondition 'Only applies when the render engine is EEVEE' gives real context for when the tool is valid, but there is no guidance about when to prefer this over set_light_property or set_shadow_settings, and no statement about what happens if the engine is not EEVEE.

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