Skip to main content
Glama

unreal_set_environment_settings

Set environment, fog, and sky settings in an Unreal Engine 5 project to control atmospheric lighting and mood. Use it to configure scene atmosphere directly from your AI client.

Instructions

Set environment/fog/sky 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_environment_settings"
  }
}

Input Schema

NameRequiredDescriptionDefault
paramsYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.9/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; it only implies a mutation via 'Set'. It says nothing about required permissions, whether changes are persistent vs. editor-session-only, whether they apply to PIE, or whether the operation is reversible — all critical context for a settings mutation with zero annotation coverage.

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 single sentence is short and front-loaded, but its brevity reflects under-specification rather than economy — there is no useful information to compress. Nothing about what settings are set, what the params object holds, or what happens on success.

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?

Although an output schema exists (so return values need not be explained), the definition leaves the essential input — a free-form 'params' object — completely undocumented, and with no annotations the behavioral picture is blank. For a mutation tool with an opaque payload, this is far short of what an agent needs to invoke it 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?

There is a single required parameter, 'params', typed as an unconstrained object with 0% schema description coverage, and the description says nothing about its structure or contents. The agent has no way to know what keys the object expects, making this parameter effectively opaque.

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 has a specific verb ('Set') and names the resource domain ('environment/fog/sky settings'), which hints at how it differs from siblings like unreal_set_render_settings or unreal_set_world_settings. However, it never specifies which concrete settings are covered or where the environment/fog/sky boundary lies, so the agent only gets a vague category, not a precise capability.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/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 prerequisites, and no mention of the many sibling settings tools. The agent is left to guess whether this overlaps with unreal_set_render_settings or unreal_set_world_settings, and the description offers no exclusions or alternative routing.

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