Skip to main content
Glama

get_light_info

Retrieves light data from a Blender scene, optionally filtered by name, so you can inspect existing lighting settings and verify a scene’s setup.

Instructions

Get light information.

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": "get_light_info"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.8/5.0
Behavior1/5

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

With no annotations, the description carries the full burden of behavioral disclosure and delivers none: no mention of read-only semantics, what happens if 'name' is omitted or doesn't match a light, error behavior, or scope of returned data. "Get ... information" adds nothing an agent couldn't infer from the tool name.

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?

The sentence is short but that is under-specification rather than conciseness: it wastes the only sentence on restating the name instead of front-loading scope or filtering behavior.

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?

An output schema exists so return values needn't be explained, but for a tool with an optional filter parameter and many related siblings the description omits everything an agent needs to call it correctly and interpret it, leaving it effectively undocumented.

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

Parameters2/5

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

Schema description coverage is 0% and the description does not mention the single optional 'name' parameter at all, so it provides no meaning beyond the schema. The parameter's name is somewhat self-explanatory, which keeps this above 1, but there is no guidance on default behavior when name is null.

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?

"Get light information" only restates the tool name (get_light_info) with no added specificity: it doesn't say whether it returns properties of one named light or a summary, nor how it differs from siblings like get_lights or get_object_info. It is a near-tautology rather than a distinguishing statement of purpose.

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 is given: nothing says when this should be called instead of get_lights (the plural listing sibling) or whether it requires a light to exist/be selected. The agent must infer usage 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