Skip to main content
Glama

unreal_get_scene_statistics

Retrieve scene statistics from an Unreal Engine 5 project to inspect level content and support diagnostics or optimization decisions.

Instructions

Get scene statistics.

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

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 provided, so the description carries the full behavioral burden, yet it discloses nothing about cost, whether the scene must be loaded, permissions, or what the statistics cover. The only mitigating factor is the presence of an output schema, which lets the description off the hook for explaining return values.

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 sentence is short and front-loaded, but this is under-specification rather than conciseness — there is no structure or content to speak of. Nothing is wasted because almost nothing is said.

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?

Given an opaque one-parameter schema, no annotations, and no usage context, the definition is too thin to tell an agent how or when to call it correctly. The existing output schema covers the return side, but the input and behavioral sides remain empty.

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 untyped, undocumented "params" object with 0% schema description coverage, and the description says nothing about what it should contain. With low coverage the description is expected to compensate, and it adds no meaning at all beyond the schema.

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 "Get scene statistics" is essentially a restatement of the tool name unreal_get_scene_statistics, with no further specification. It does not clarify what kind of statistics (performance, actor counts, memory, render stats) or how they differ from siblings like unreal_get_scene_hierarchy.

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 exclusions, and no mention of alternatives such as unreal_get_scene_hierarchy or unreal_build_scene. The agent must infer the tool's role entirely from its 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