Skip to main content
Glama

unreal_get_lighting_info

Retrieve lighting actor information from an Unreal Engine 5 project to inspect light types, properties, and placement for scene setup or debugging.

Instructions

Get lighting actors info.

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": {
      "params": "<params>"
    },
    "name": "unreal_get_lighting_info"
  }
}

Input Schema

NameRequiredDescriptionDefault
paramsYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.1/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 bare verb: no indication that it is a read-only query, no scope constraints (level-wide vs. selection), no mention of whether it requires an editor session. The only mitigating factor is the presence of an output schema, which covers return shape.

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 single sentence contains no filler, but it is under-specified rather than concise—six words that convey almost nothing an agent needs. Brevity here reflects missing content, not efficiency.

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?

With an opaque untyped params object, zero annotation coverage, and no parameter documentation, the definition leaves the most important calling detail unspecified. The output schema covers returns, but the input side is effectively undocumented.

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 is one required parameter named "params" with no type, no properties, and 0% schema description coverage. The description adds no meaning whatsoever about what this object should contain, leaving the agent unable to construct a valid call without trial and error.

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

Purpose3/5

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

States a verb and resource ("Get lighting actors info"), so the agent knows it retrieves lighting-related actor data. But "info" is undefined and there is no differentiation from nearby tools such as unreal_setup_lighting or the other unreal_get_*_info siblings, all of which follow the identical naming pattern.

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?

The description contains no when-to-use guidance, no exclusions, and no mention of any alternative tool. An agent must guess whether this is the right call versus unreal_setup_lighting or another getter.

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