Skip to main content
Glama

unreal_get_scene_hierarchy

Inspect actor attachment hierarchy to understand parent-child relationships in an Unreal Engine 5 scene and diagnose attachment or transform issues.

Instructions

Inspect actor attachment hierarchy.

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

Input Schema

NameRequiredDescriptionDefault
paramsYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.4/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, and it discloses almost nothing. "Inspect" weakly implies a read, but there is no statement about side effects, whether the whole scene or a filtered subset is walked, depth/recursion limits, or performance cost on large scenes.

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?

A single six-word sentence with zero redundancy and nothing to trim, which is good for scanning, but the brevity comes at the cost of under-specification rather than efficiency. The key scope information is absent rather than front-loaded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/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-value shape needn't be explained, and the tool has only one parameter, which limits the surface area. Still, with no annotations and an undocumented params object, the definition leaves the agent without enough to invoke the tool confidently beyond guessing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

There is one required parameter with 0% schema description coverage and it is an opaque, untyped "params" object, so neither the schema nor the description explains what must be supplied. The description adds no meaning about whether params scope by level, actor, root, or depth.

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 gives a verb ("Inspect") and a resource ("actor attachment hierarchy"), so the general subject is graspable, but "Inspect" is generic and there is no differentiation from close siblings like unreal_get_bone_hierarchy or unreal_get_component_hierarchy. It also doesn't clarify the relationship between the tool name's "scene hierarchy" and the described "actor attachment" 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 guidance, no exclusions, and no mention of alternatives such as the bone or component hierarchy tools. The agent must infer usage entirely from the name and from sibling names, which the context notes say should not be used to establish behavior.

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