Skip to main content
Glama

daz_list_morphs

Discover morphs available on a DAZ figure by listing all numeric properties or only currently active morphs. Accepts node label and an option to include zero values.

Instructions

List all morphs (numeric properties) on a node.

Returns all numeric properties on a node, which includes morphs (body shapes, facial expressions), transforms, and other numeric dials. Useful for discovering what morphs are available on a figure.

Args: node_label: Display label or internal name of the node (e.g., "Genesis 9"). include_zero: If True, return all morphs including those set to 0. If False (default), only return morphs with non-zero values (currently active morphs).

Returns:

  • morphs: List of morph objects with:

    • label: Display label (e.g., "Head Size")

    • name: Internal name (e.g., "HeadSize")

    • value: Current numeric value

    • path: Property path for organization (e.g., "Morphs/Head")

  • count: Number of morphs returned

  • nodeLabel: Confirmed node label

Example: # List only active morphs on Genesis 9 result = daz_list_morphs("Genesis 9", include_zero=False) # result["morphs"] = [ # {"label": "Height", "name": "Height", "value": 1.05, "path": "Morphs/Body"}, # {"label": "Head Size", "name": "HeadSize", "value": 0.9, "path": "Morphs/Head"} # ]

# List all available morphs (including zero values)
result = daz_list_morphs("Genesis 9", include_zero=True)
# result["count"] might be 500+ morphs

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
node_labelYes
include_zeroNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior5/5

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

No annotations exist, so description carries full burden. It comprehensively discloses behavior: returns all numeric properties, includes morphs/transforms, details return structure with example, and explains the include_zero parameter's impact on returned morphs.

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 well-structured with Args, Returns, and Example sections. It is informative but slightly verbose; could be marginally more concise. However, every sentence adds value.

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 (2 params, no nested objects), the description is complete. It includes parameter explanations, return structure, and a realistic example. The output schema exists but description's Returns section covers it adequately.

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?

Schema coverage is 0%, so description provides full semantics. It explains node_label as display label or internal name with example, and include_zero with clear True/False behavior. This adds complete meaning beyond the raw 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 lists all numeric properties (morphs, transforms) on a node, with precise verb 'list' and resource 'numeric properties'. It distinguishes from sibling tool daz_search_morphs by indicating this is for discovery of all available morphs, not searching.

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 notes usefulness 'for discovering what morphs are available on a figure' and explains the include_zero parameter's effect. However, it does not explicitly state when not to use or provide alternative sibling tools for specific morph search.

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