Skip to main content
Glama

daz_batch_select

Select multiple DAZ Studio scene nodes by providing a list of node labels, with option to add to current selection.

Instructions

Select multiple nodes in the DAZ Studio scene.

Args: node_labels: List of node display labels to select. add_to_selection: If True, add to current selection; if False, replace current selection (default: False).

Returns:

  • selected: Array of node labels that were successfully selected

  • count: Number of nodes selected

  • total: Total number of node labels provided

Example: # Select multiple characters daz_batch_select(["Genesis 9", "Genesis 8 Female"])

# Add props to current selection
daz_batch_select(["Sword", "Shield"], add_to_selection=True)

# Select all lights in scene
daz_batch_select(["Spot Light 1", "Distant Light 1", "Point Light 1"])

Note: Selection affects which nodes appear in the Scene/Parameters panes in DAZ Studio. Some operations apply to the current selection. Nodes that don't exist are silently skipped.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
node_labelsYes
add_to_selectionNo

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 that non-existent nodes are silently skipped and explains the add_to_selection behavior. It also notes the effect on DAZ Studio UI, providing sufficient behavioral context for a non-destructive tool.

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 well-structured with Args, Returns, Example, and Note sections. It is concise and every sentence adds value without redundancy.

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 moderate complexity (2 parameters, output schema present), the description covers all necessary aspects: purpose, parameters, return values, examples, and behavioral notes. It is complete.

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?

Schema coverage is 0%, so description compensates well. It defines node_labels as 'list of node display labels to select' and add_to_selection with its effect and default. Examples further clarify usage.

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 'Select multiple nodes in the DAZ Studio scene.' It uses a specific verb ('select') and resource ('nodes'), and the examples distinguish it from sibling tools like daz_batch_visibility or daz_batch_transform.

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 explains that selection affects UI panes and that some operations apply to the current selection, providing context for when to use. However, it does not explicitly exclude scenarios or mention alternatives for single-node selection.

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