Skip to main content
Glama

unreal_create_spot_light

Creates a spot light in an Unreal Engine 5 level to add directional, cone-shaped lighting for scenes or assets.

Instructions

Create a spot 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_spot_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/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 disclosure burden, and it discloses nothing. It does not say whether the actor is added to the current level, whether it requires an editor connection, what the returned handle is, or how the opaque 'params' payload affects behavior.

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?

Four words, front-loaded, with zero wasted language. It is efficient but under-sized for a tool whose sole parameter is completely opaque, so brevity here reflects under-specification rather than discipline.

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 with no annotations and a 0%-documented parameter the description should compensate and does not. For a creation/mutation tool, an agent cannot determine required context or payload shape from this definition.

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 'params' is an untyped, undescribed object. The description adds no information about what fields (location, rotation, intensity, color, attenuation) that object expects, leaving the caller blind on the only input.

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 description states a specific verb and resource ("Create a spot light"), which does distinguish it from siblings like unreal_create_point_light or unreal_create_rect_light by name. However, it gives no scope details — where the light is created, in which level/actor context, or what a spot light implies versus other light types. Minimum-viable clarity only.

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 mention of alternatives (point vs rect vs directional light), and no prerequisites such as an open editor session or an active level. The agent must infer everything from the tool name alone.

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