Skip to main content
Glama

unreal_create_sky_atmosphere

Create a sky atmosphere actor in an Unreal Engine 5 level to set up physically based atmospheric lighting and sky rendering for your scene.

Instructions

Create a sky atmosphere actor.

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

Input Schema

NameRequiredDescriptionDefault
paramsYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.6/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries the full behavioral burden and adds nothing: it does not say whether the actor is spawned at a default transform, whether it requires an open level or editor connection, whether the operation is reversible, or what failure conditions look like. An output schema exists, which slightly reduces the need to describe returns, but side effects and preconditions remain undisclosed.

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?

One short, front-loaded sentence with no filler or redundancy. It is efficient, though its brevity reflects under-specification rather than disciplined editing.

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?

For an editor-mutating actor-creation tool with an unspecified params object, the definition is not complete enough: the agent learns what is created but not how to parameterize it or what environment it requires. The presence of an output schema covers return values but not the missing input and precondition detail.

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 parameter is an opaque object named 'params' with 0% schema description coverage, and the description says nothing about what belongs inside it. With one undocumented parameter the 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.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific verb (Create) and a specific resource (sky atmosphere actor), so the agent knows exactly what object is produced. It does not differentiate from close siblings such as unreal_create_sky_light or unreal_create_exponential_height_fog, leaving the choice to the agent's own knowledge of sky atmosphere semantics.

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 statement of prerequisites such as an open level or an editor session, and no reference to any alternative tool. The agent must infer entirely from the tool name that this is the way to add atmospheric scattering rather than a light actor.

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