Skip to main content
Glama

daz_search_morphs

Search for morphs matching a substring pattern on a DAZ Studio node to locate specific morphs like facial expressions or body parts. Returns matching morphs with labels, values, and paths.

Instructions

Search for morphs matching a name pattern.

Search through all numeric properties (morphs) on a node for those matching a substring pattern. Useful for finding specific morphs like all facial expressions, body morphs, or morphs for a specific body part.

Args: node_label: Display label or internal name of the node (e.g., "Genesis 9"). pattern: Substring to search for in morph label or name (case-insensitive). Examples: "smile", "head", "muscle", "express" include_zero: If True, return all matching morphs including zero values. If False (default), only return matching morphs that are active.

Returns:

  • morphs: List of matching morph objects with:

    • label: Display label

    • name: Internal name

    • value: Current value

    • path: Property path

  • count: Number of matching morphs

  • pattern: The search pattern used

  • nodeLabel: Confirmed node label

Example: # Find all smile-related morphs result = daz_search_morphs("Genesis 9", "smile", include_zero=True) # result["morphs"] might include: "Smile", "Smile Open", "Smile Closed", etc.

# Find active head morphs
result = daz_search_morphs("Genesis 9", "head", include_zero=False)
# Only returns head morphs with non-zero values

# Find all facial expression morphs
result = daz_search_morphs("Genesis 9", "express", include_zero=True)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
node_labelYes
patternYes
include_zeroNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior4/5

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

No annotations are provided, so the description carries full burden. It describes that the tool searches all numeric properties, returns morph details (label, name, value, path), and explains the include_zero parameter behavior. It does not mention side effects, but 'Search' implies read-only. The return structure is well-documented.

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 a clear summary, args, returns, and examples. It is front-loaded with the main purpose. While thorough, it is slightly verbose but earns its length due to complexity.

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 has 3 parameters, no annotations, and an output schema, the description covers all aspects: input params, return structure (morphs, count, pattern, nodeLabel), and usage examples. It is complete for a search tool.

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?

With 0% schema description coverage, the description fully explains each parameter: node_label (display or internal name), pattern (substring, case-insensitive, examples), and include_zero (behavioral difference). Detailed examples demonstrate usage effectively.

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 'Search for morphs matching a name pattern' and explains it searches through numeric properties on a node. Examples show finding specific morphs like facial expressions, body morphs, or morphs for a specific body part. This differentiates it from siblings like daz_list_morphs by adding pattern matching and substring search.

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 clear context on when to use this tool (finding specific morphs by pattern) with multiple examples. However, it does not explicitly mention when not to use it or compare with alternatives like daz_list_morphs.

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