Skip to main content
Glama

create_light

Add a configurable light source to a Blender scene by setting type, color, energy, and location. Useful for lighting 3D models and scenes before rendering.

Instructions

Create a light.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

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

Input Schema

NameRequiredDescriptionDefault
nameNo
colorNo
energyNo
locationNo
light_typeNoPOINT

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.7/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure and fails to meet it: it does not say the light is added to the scene, whether it is selected/active afterwards, what defaults apply, or what permissions/context are required. Only the bare implication of a mutating create is conveyed.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is short, but short here reflects under-specification rather than efficiency: a single content-free sentence with no front-loaded constraints or structure. Nothing in the sentence helps an agent decide or parameterize a call.

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?

Although an output schema exists so return values need not be explained, a five-parameter creation tool with zero annotation coverage and zero schema descriptions needs the description to supply defaults, parameter meaning, and the effect of the call. Virtually all of that is missing.

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

Parameters1/5

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

There are five parameters (name, color, energy, location, light_type) with 0% schema description coverage, and the description mentions none of them. Critically, light_type defaults to "POINT" with no enumeration of valid values and no hint of what the color/location arrays represent (RGB? XYZ?), leaving callers unable to construct valid input from the documentation alone.

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

Purpose2/5

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

"Create a light" does pair a verb with a resource, but it is effectively a restatement of the tool name create_light and gives no scope (what kind of light object, where it lands, what it returns). Nothing distinguishes it from siblings such as create_lighting_setup or create_object.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

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

The description offers no when-to-use guidance, no preconditions, and no alternatives, even though sibling tools like create_lighting_setup and create_object exist in the same family. An agent must guess entirely from the name.

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