Skip to main content
Glama

unreal_create_rect_light

Creates a rectangular area light in Unreal Engine 5 so you can add controlled, shape-based illumination to a scene.

Instructions

Create a rect 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_rect_light"
  }
}

Input Schema

NameRequiredDescriptionDefault
paramsYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.4/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 entire burden of behavioral disclosure. It implies a mutating editor operation but says nothing about required editor state, defaults applied to the new light (color, intensity, transform), undo behavior, or what happens if creation fails. Only the bare mutation intent is conveyed.

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?

One front-loaded sentence with zero padding, so there is no wasted wording. The brevity is a symptom of under-specification rather than discipline, but nothing needs trimming.

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 do not need describing, but the opaque 'params' argument means the definition is not sufficient to invoke the tool correctly. For a creation tool in a family of sibling light creators, the description should at minimum indicate the required parameters or defaults.

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 'params' property is typed only as a bare object with no fields defined. The description adds no information about what must go inside params, leaving the agent unable to construct a valid call from either source.

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

Purpose4/5

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

The description states a specific verb plus resource ('Create a rect light'), which is enough to separate it from siblings like unreal_create_point_light and unreal_create_spot_light through the resource noun alone. It stops short of any scope or behavioral detail, so it is clear but undifferentiated beyond the name.

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 guidance on when to choose a rect light over the point, spot, directional, or sky light siblings, and no prerequisites or exclusions are mentioned. The agent must infer placement from the tool name only.

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