Skip to main content
Glama

daz_get_node_hierarchy

Retrieve the complete hierarchy tree for a node, showing all descendants. Use to analyze skeleton structures, bone relationships, or complex scene hierarchies with configurable depth limits.

Instructions

Get complete hierarchy tree for a node with all descendants.

Returns the full hierarchical structure of a node, including all children, grandchildren, etc. Useful for understanding skeleton structure, bone relationships, and complex scene hierarchies.

Args: node_label: Display label or internal name of the root node. max_depth: Maximum recursion depth (default 10, 0 = unlimited). Use to limit deep hierarchies (e.g., Genesis 9 skeleton has 100+ bones).

Returns:

  • node: Root node label

  • hierarchy: Nested structure with:

    • label: Node display label

    • name: Internal name

    • type: DazScript class name

    • children: List of child hierarchies (recursive)

  • totalDescendants: Total number of descendants

Example: # Get skeleton hierarchy with depth limit result = daz_get_node_hierarchy("Genesis 9", max_depth=3) # Returns nested structure: hip -> abdomen -> chest -> ...

# Get full hierarchy (warning: can be large)
result = daz_get_node_hierarchy("Genesis 9", max_depth=0)
# Returns complete skeleton with all 100+ bones

# Get prop hierarchy
result = daz_get_node_hierarchy("Sword", max_depth=5)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
node_labelYes
max_depthNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior4/5

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

With no annotations, the description discloses the return format (nested structure with children recursively), includes totalDescendants count, and warns about large output for max_depth=0. It does not mention side effects or performance, but for a read tool this is adequate.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is well-structured with sections for Args, Returns, and Examples, and is front-loaded with the main purpose. Every sentence adds value, though it could be slightly more concise without losing clarity.

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

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given 2 parameters, an output schema, and the description covering return structure, usage tips, and multiple examples, the tool definition is complete for its purpose. It addresses typical use cases and potential pitfalls.

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

Parameters5/5

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

Despite 0% schema description coverage, the description fully explains both parameters: node_label is the display label or internal name, max_depth has a default of 10 and effect (0=unlimited). It provides practical tips like limiting depth for deep hierarchies, adding significant value beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool gets the complete hierarchy tree for a node with all descendants, specifying the verb 'get' and the resource 'hierarchy tree'. It distinguishes itself from sibling tools like daz_get_node or daz_list_children by returning the full nested structure recursively.

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

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides context on when to use the tool (e.g., understanding skeleton structure, bone relationships) and includes examples with different use cases (depth-limited, full hierarchy). It warns about large outputs for deep hierarchies but does not explicitly exclude alternatives, though the purpose is clear enough.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/bluemoonfoundry/daz-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server