Skip to main content
Glama

unreal_set_light_temperature

Sets a light's color temperature in Unreal Engine 5, letting you warm or cool lighting for a scene through the editor bridge.

Instructions

Set light temperature.

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

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
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 disclosure burden and does not meet it. It does not say whether the change is immediate or reversible, whether it requires a selected actor, what units the temperature uses, or what happens on failure.

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?

Three words are concise to the point of under-specification. There is no structure to front-load because nothing beyond the bare action is present.

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?

A mutation tool with zero annotation coverage, a completely opaque parameter object, and no guidance is not callable with confidence. An output schema exists, so return values need not be described, but everything about the input and side effects is missing.

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 parameter is an untyped "params" object with no properties declared. The description supplies nothing to compensate — no mention of actor reference, temperature value, units, or accepted range — leaving the caller unable to construct a valid call.

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?

"Set light temperature" names a verb and a resource, so the agent knows this mutates a light's color temperature. However, it is essentially the tool name restated in prose and offers no differentiation from siblings such as unreal_set_light_color or unreal_set_light_intensity.

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 (e.g. an existing light actor must be targeted), and no reference to the sibling tools that set color or intensity instead. The agent must infer the entire routing decision from the 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