Skip to main content
Glama

unreal_get_component_hierarchy

Inspect an Unreal Engine actor’s component hierarchy to understand its parent-child structure and support editing or debugging.

Instructions

Inspect component 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_component_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.3/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full burden, and it discloses almost nothing. "Inspect" weakly implies a read, but there is no statement of whether the traversal is recursive, what happens with unloaded actors, or whether the required params object must identify an actor, blueprint, or component.

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 contains no padding and is trivially front-loaded, so it is concise. However, terseness here reflects under-specification rather than economy, since nothing substantive is delivered.

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 values need not be explained in prose. The critical gap is on the input side: the required params object is completely opaque, with no annotations to compensate, which is inadequate for an agent to call this 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?

Schema description coverage is 0% and the single required parameter is an untyped, property-less object named "params," so the schema gives the agent no structured meaning at all. The description says nothing about what that object must contain, leaving the agent unable to construct a valid call.

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?

Names a verb ("inspect") and a resource ("component hierarchy"), so the general purpose is graspable, but it never says whose components or which hierarchy level, leaving it ambiguous against siblings such as unreal_get_actor_components, unreal_get_scene_hierarchy, and unreal_get_bone_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 mention of prerequisites, and no pointer to an alternative tool. The agent must infer from the name alone whether this is the right call versus unreal_get_actor_components or unreal_get_scene_hierarchy.

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