Skip to main content
Glama

unreal_create_sky_light

Creates a sky light actor in an Unreal Engine 5 level to supply ambient lighting. Use it to add realistic indirect light to your scene.

Instructions

Create a sky 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_sky_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.2/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 full behavioral burden, and it discloses nothing about side effects, required editor context, or whether the created actor is selected/registered in the level. Only the verb 'Create' implies a mutation, and even that is not stated explicitly as a scene-modifying operation.

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, so it is concise in the literal sense. But the brevity here is under-specification rather than efficiency; nothing else is offered to earn the sentence's place beyond restating 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 described. Still, for an actor-creation tool with an opaque required 'params' object and no annotations, the definition omits everything an agent needs: what the params contain, prerequisites, and what changes in the level.

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 schema has one required parameter, 'params', with 0% description coverage and no defined properties. The description adds no information whatsoever about what belongs in that object, so an agent has no way to construct a valid call from the definition alone.

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 names a specific verb and resource ('Create a sky light'), which is more than a tautology and nominally distinguishes it from the light-creation siblings. However, it never explains what a sky light is or how it differs from unreal_create_sky_atmosphere or unreal_create_directional_light, so an agent must already know Unreal's lighting model to pick correctly.

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 exclusions, and no mention of alternatives such as sky atmosphere or the other light types. The agent is left to infer selection criteria entirely from the tool name.

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