Skip to main content
Glama

modify_light

Adjust the settings of a named Blender light to control brightness, color, and other scene lighting parameters.

Instructions

Modify light settings.

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>",
      "settings": "<settings>"
    },
    "name": "modify_light"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
settingsYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.9/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden, yet it discloses nothing beyond the implication of mutation. It does not state whether changes are destructive, whether omitted settings are preserved, what permissions/lookups are needed, or how the light is identified.

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

Conciseness3/5

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

The single sentence is front-loaded and free of waste, but its brevity comes from omitting content rather than from disciplined editing. There is no structure to speak of because there is almost no content.

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

Completeness1/5

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

An output schema exists so return values need not be described, but the definition leaves the core gap untouched: an untyped nested settings object with zero documentation on a mutation tool with no annotations. For a two-required-parameter write operation this is far from sufficient to invoke correctly.

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?

Schema description coverage is 0% and both parameters are required. The 'settings' parameter is a free-form object with additionalProperties: true, and the description says nothing about what keys it accepts, so an agent has no way to construct a valid call; 'name' is also unexplained (object name vs. lookup key).

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?

"Modify light settings" essentially restates the tool name modify_light with no added specificity: it never says which light properties can be changed (energy, color, type, position) or how it differs from siblings like create_light, delete_light, or modify_object.

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 when-to-use guidance, no prerequisites, and no mention of alternatives such as delete_light or get_light_info. An agent must infer that this is the editable counterpart to create_light purely 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