Skip to main content
Glama

unreal_create_point_light

Create a point light actor in an Unreal Engine 5 level via UnrealEngineMCP to add local lighting to scenes and environments during AI-assisted editor workflows.

Instructions

Create a point 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_point_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.8/5.0
Behavior1/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 of behavioral disclosure, and it says nothing about permissions, editor state requirements, side effects, or defaults. It does not disclose where the light is placed, what happens on failure, or how the created actor is returned.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The single sentence is short and front-loaded with no filler. However, it is concise to the point of under-specification rather than being well-structured information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, which absolves the description of explaining return values, but for a creation tool with an entirely undocumented params object and no annotations, this definition is far too thin. It omits everything an agent needs in order to invoke the tool correctly.

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?

The single required parameter is an untyped nested "params" object with 0% schema description coverage, and the description does not mention it at all. The agent has no way to know what light properties (location, intensity, color, mobility) the params object accepts.

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 point light" only restates the tool name (unreal_create_point_light) with no added scope. It does not distinguish this tool from the sibling light creators (directional, rect, sky, spot), so an agent learns nothing beyond the identifier.

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 prerequisites such as an open level or editor context, and no comparison to the other light-creation or light-property tools. The definition supplies no guidance at all beyond the bare statement of intent.

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