Skip to main content
Glama

unreal_set_shadow_settings

Configure light shadow settings in Unreal Engine 5 to control shadow quality and behavior, helping you tune lighting for a scene through the MCP editor bridge.

Instructions

Set light shadow settings.

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

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 behavioral burden. Beyond the mutation implied by "Set," it discloses nothing: not whether changes are reversible, not what permissions or editor state are required, not which shadow properties exist, and not how to undo or verify the change.

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?

The sentence is short and front-loaded, but that brevity reflects under-specification rather than efficiency. There is no structure, no examples, and no detail that would earn the sentence a place beyond restating the tool name.

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?

For a mutation tool with no annotations and an opaque untyped params object, the description provides none of the missing context. An output schema exists, so return values need not be explained, but the input contract and behavioral consequences remain entirely undocumented.

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?

There is a single required parameter named "params" with no type, no properties, and 0% schema description coverage, and the description adds no information about what belongs in it. An agent has essentially no way to construct a valid call from either the schema or the description.

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 verb and a resource ("Set light shadow settings"), which separates it loosely from siblings like unreal_set_light_color or unreal_set_light_intensity. However, it is vague about scope: it never says whether this affects one light (and which one) or global shadow configuration, so the agent cannot distinguish it confidently from unreal_set_render_settings or unreal_set_environment_settings.

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?

The description gives no when-to-use guidance, no preconditions, and no alternatives. Nothing tells the agent which light or actor the settings apply to, or when to prefer this over the render/environment settings siblings.

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