Skip to main content
Glama

unreal_setup_lighting

Set up a basic lighting environment in an Unreal Engine 5 project by configuring sky, fog, and directional light intensity for scene illumination.

Instructions

Set up a basic lighting environment.

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_setup_lighting"
  }
}

Input Schema

NameRequiredDescriptionDefault
paramsYes
include_fogNo
include_skyNo
directional_intensityNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.2/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, and it discloses almost nothing. It does not say whether existing lights are replaced or augmented, whether the action is reversible, what 'basic' means in terms of actors spawned, or whether it requires an editor session.

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 padding, but its brevity comes from under-specification rather than economy. There is room to add substantive detail without becoming verbose.

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 need not be described, but for a mutation tool with four undocumented parameters and zero annotation coverage the description is far too thin. Key facts an agent needs to call it safely are 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?

Schema description coverage is 0% across four parameters, including a required untyped 'params' object with no title or description. The single sentence adds no meaning for include_fog, include_sky, directional_intensity, or params, leaving an agent to infer everything from property names and defaults.

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?

The verb 'set up' plus resource 'lighting environment' indicates the domain, but 'basic' is undefined and nothing distinguishes it from the sibling getter unreal_get_lighting_info beyond the verb. An agent can guess this is a creation/configuration action but cannot tell what it actually produces.

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 (e.g. whether a level must be open), and no mention of alternatives or follow-up tools. The only implied usage comes from the tool name and its pairing with the lighting-info 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