Skip to main content
Glama

daz_list_children

List the immediate children of any node in a DAZ Studio scene to explore hierarchy one level at a time or verify if a node has children.

Instructions

List direct children of a node.

Returns only the immediate children (not grandchildren). Useful for exploring hierarchy one level at a time or checking if a node has children.

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

Returns:

  • node: Parent node label

  • children: List of child objects with:

    • label: Child display label

    • name: Child internal name

    • type: DazScript class name

  • count: Number of children

Example: # List children of Genesis 9 root result = daz_list_children("Genesis 9") # Returns: [{"label": "hip", "name": "hip", "type": "DzBone"}]

# Check if node has children
result = daz_list_children("Camera 1")
# result["count"] == 0 means no children

# List bones under hip
result = daz_list_children("hip")
# Returns: pelvis, lThighBend, rThighBend

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
node_labelYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior4/5

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

The description discloses that the tool returns only direct children and provides detailed return structure including count and example outputs. With no annotations, it carries the full burden well. However, it does not mention error behavior for invalid node labels.

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

Conciseness5/5

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

The description is concise and well-structured: purpose statement, usage hint, parameter definition, return structure, and three examples. Every sentence adds value, and it is front-loaded with the core action.

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 the tool's simplicity (one parameter, clear output), the description covers all necessary information: what it does, when to use it, how to specify the parameter, what the output looks like, and practical examples. No annotations are needed for this context.

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?

The input schema has no description for the parameter, but the tool description explains 'node_label: Display label or internal name of the parent node.' This adds critical meaning beyond the schema's mere string type, fully compensating for the 0% schema coverage.

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 'List direct children of a node' and specifies 'Returns only the immediate children (not grandchildren)'. This distinguishes it from sibling tools like daz_get_node_hierarchy which returns full hierarchy, making purpose specific and unambiguous.

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: 'Useful for exploring hierarchy one level at a time or checking if a node has children.' This implies when to use it. However, it does not explicitly mention when not to use it or name alternative tools, so it falls short of a 5.

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