Skip to main content
Glama

unreal_create_directional_light

Create a directional light in an Unreal Engine 5 project to illuminate large outdoor scenes with parallel, sun-like lighting.

Instructions

Create a directional light.

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

Input Schema

NameRequiredDescriptionDefault
paramsYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.5/5.0
Behavior1/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: not that this is a mutating operation, not what actor is created or where it is placed in the level, not whether it is undoable, and not what permissions or editor state are required.

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 and front-loaded, but its brevity reflects under-specification rather than conciseness. Every substantive fact an agent needs has been omitted, so nothing in it earns its place beyond echoing the name.

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 explained, but the tool complexity still demands more: a 1-param mutation with a fully opaque params object and zero annotations leaves the agent unable to call it correctly. The description supplies none of the missing context.

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 the single required parameter is a generic untyped "params" object whose structure is entirely undocumented. The description adds no information about what belongs inside params (transform, intensity, color, mobility, name), leaving the agent with no way to construct a valid call.

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 directional light" is a restatement of the tool name unreal_create_directional_light rather than an explanation of what the tool produces. It does not distinguish this tool from the many sibling light-creation tools (point, rect, sky, spot), so an agent learns nothing about the directional-specific behavior.

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?

There is no when-to-use guidance, no mention of when a directional light is preferred over a point/spot/rect/sky light, and no prerequisites such as requiring an open level or actor context. Any routing decision between the light-creation siblings is left entirely to inference from tool names.

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