Skip to main content
Glama

daz_get_parent

Retrieve the parent node of a given node in the scene hierarchy. Useful for navigating upward through parent-child relationships.

Instructions

Get parent node of a node.

Returns the immediate parent of a node, or null if the node is a root node (no parent). Useful for traversing hierarchy upward.

Args: node_label: Display label or internal name of the child node.

Returns:

  • node: Child node label

  • parent: Parent node object with label, name, type, or null if no parent

Example: # Get parent of a bone result = daz_get_parent("lHand") # Returns: {"parent": {"label": "lForearmBend", "name": "lForearmBend", ...}}

# Check if node is root (has no parent)
result = daz_get_parent("Genesis 9")
# result["parent"] == null

# Traverse hierarchy upward
node = "lIndex3"
while True:
    result = daz_get_parent(node)
    if not result["parent"]:
        break
    print(f"Parent of {node}: {result['parent']['label']}")
    node = result["parent"]["label"]

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
node_labelYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior3/5

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

No annotations exist, so description carries full burden. It specifies return null for root nodes and provides example outputs, but lacks details on permissions, side effects, or limitations.

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?

Description is fairly long with detailed Args/Returns and examples, but well-structured and front-loaded with purpose. Could be slightly more concise but value justifies length.

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

Completeness4/5

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

Given the simple tool with output schema, description covers return format, edge case (null for root), and usage examples. No major gaps.

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

Parameters4/5

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

The single parameter node_label has 0% schema description coverage; the description adds meaning by explaining it can be a display label or internal name, going 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 'Get parent node of a node' and distinguishes from siblings like daz_get_node_hierarchy and daz_list_children by focusing on immediate parent retrieval.

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?

It provides clear usage context ('useful for traversing hierarchy upward') and concrete examples, but does not explicitly state when not to use or mention alternatives.

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