Skip to main content
Glama

unreal_set_render_settings

Configure supported Unreal Engine render settings to control visual output and adjust rendering behavior during AI-assisted editor workflows.

Instructions

Set supported render 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_render_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.2/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden and discloses almost nothing: it does not say whether this requires editor/game-thread context, whether a partial params blob merges or replaces existing settings, whether changes persist across sessions, or whether the operation can fail. Only the bare implication of a mutation is conveyed.

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?

It is a single short sentence, front-loaded with the verb, so there is no padding. The brevity is not efficient compression, however — it reflects under-specification rather than conciseness.

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 a mutation tool with an opaque nested params blob, no annotations, and no parameter documentation, the description should at minimum enumerate the supported settings or point to a schema reference. An output schema exists, so return values need not be explained, but the input side is entirely unexplained.

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 is an undescribed, untyped object named "params" with 0% schema description coverage, and the description adds no information about its expected keys or shape. An agent cannot construct a valid call from this definition without trial and error.

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 supported render settings" gives a verb (Set) and a resource (render settings), and the get/set prefix distinguishes it from unreal_get_render_settings. However, "supported" is undefined — the agent cannot tell what settings are covered or how this differs from unreal_set_shadow_settings or unreal_set_environment_settings, which may overlap.

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 offers no when-to-use guidance, no prerequisites, and no mention of when the get counterpart or the more specific shadow/environment setters should be preferred. The agent must infer usage entirely 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