Skip to main content
Glama

unreal_optimize_scene

Analyze Unreal Engine 5 scene performance and generate actionable optimization recommendations to address rendering bottlenecks.

Instructions

Analyze scene performance and recommend optimization actions.

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

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 burden. It says 'analyze' and 'recommend', which hints at a non-mutating advisory operation, but the name implies scene modification and the text never confirms whether anything is applied, whether it requires a loaded level, or how expensive the analysis is.

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?

One short, front-loaded sentence with no filler. Its brevity is a symptom of under-specification rather than economy, since the single sentence leaves the operative details unstated.

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 described, but that is the only burden lifted. For a tool taking an untyped params blob with no annotations, the definition says nothing about required inputs, read-vs-write behavior, or prerequisites, which is not enough 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?

The single required parameter is an opaque 'params' object with 0% schema description coverage, and the description offers no hint of what belongs inside it. An agent has no way to construct a valid call from either the schema or the prose.

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 verb 'Analyze' and the resource 'scene performance' are stated, and it adds that it recommends optimization actions. However, the tool name 'unreal_optimize_scene' suggests it may apply optimizations, while the description says only 'recommend' – that tension is never resolved, and no sibling (e.g. unreal_get_scene_statistics) is named to differentiate scope.

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 or when-not-to-use guidance and no alternative named. An agent cannot tell from the text whether this should be called before unreal_build_scene, instead of unreal_get_scene_statistics, or after profiling elsewhere.

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