Skip to main content
Glama

unreal_get_bone_hierarchy

Retrieves the bone hierarchy of a skeletal mesh so you can inspect parent-child bone relationships in Unreal Engine projects.

Instructions

Get bone 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_bone_hierarchy"
  }
}

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 supplied, so the description carries the full behavioral burden and discloses almost nothing. The verb "Get" weakly implies a read-only, non-destructive call, but there is no statement about required context (which asset/actor), whether the walk is recursive or depth-limited, or what the hierarchy is rooted at.

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?

Three words is concise, but here brevity is under-specification rather than economy; nothing is front-loaded because nothing is said. The text does not earn its place beyond a label.

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?

Because an output schema exists, the description need not explain return values, which offsets some of the gap. However, for a tool whose sole parameter is undocumented and untyped, the definition gives an agent no way to construct a valid call or know what context the query requires.

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 "params" object, so the schema conveys nothing. The description adds no information about what must go into params — presumably a target actor or skeleton reference — leaving the only input entirely unexplained.

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 states a verb and resource ("Get bone hierarchy") but is nearly a restatement of the tool name and offers no scope qualifiers. It does not distinguish this from close siblings such as unreal_get_component_hierarchy or unreal_get_scene_hierarchy, so an agent cannot tell which hierarchy query applies where.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/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 prerequisites (e.g., a selected actor or skeleton), and no mention of any alternative tool. Nothing in the text tells an agent under which conditions this tool should be chosen over the component or scene hierarchy siblings.

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