Skip to main content
Glama

unreal_create_exponential_height_fog

Creates exponential height fog in an Unreal Engine 5 level to add atmospheric depth and volumetric lighting. Use it to set fog density, height falloff, and color for outdoor scenes.

Instructions

Create exponential height fog.

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

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 provided, so the description carries the full burden, yet it discloses nothing about behavior beyond the verb 'create' — not whether the fog is added to the active level, whether duplicates are allowed, what defaults are applied, or whether the operation is reversible. Since it does not contradict anything, it is not flagged, but the disclosure is minimal.

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 short sentence is front-loaded and contains no filler, but its brevity comes from under-specification rather than efficiency. Nothing here wastes space, yet nothing earns much either.

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 explained, but the sole input parameter is completely undocumented and no behavioral context is given. For a creation tool with an opaque 'params' object, this leaves the agent unable to invoke it correctly without guesswork.

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 required parameter 'params' has 0% schema description coverage and no type information, and the description says nothing to compensate. An agent has no way to know from the definition what 'params' should contain.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

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

The description reads 'Create exponential height fog,' which simply restates the tool name unreal_create_exponential_height_fog with no additional specificity. It does not clarify what kind of object is created (an actor in the current level? a component?) or how it differs from sibling creation tools like unreal_create_sky_atmosphere or unreal_create_point_light.

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 guidance on when to use this tool, no prerequisites (e.g., a level must be open), and no mention of alternatives. The sentence is a bare statement of effect with no contextual framing.

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