Skip to main content
Glama
bluemoonfoundry

vangard-daz-mcp

by bluemoonfoundry
OverviewSchemaRelated ServersScoreDiscussions
Python
Local

daz_batch_visibility

Show or hide multiple nodes in viewport and renders to manage scene visibility, optimize render times, or test configurations.

Instructions

Show or hide multiple nodes in the viewport and renders.

Args: node_labels: List of node display labels to modify. visible: True to show nodes, False to hide them (default: True).

Returns:

  • results: Array of result objects with success, node, visible state, error

  • successCount: Number of nodes successfully modified

  • failureCount: Number of nodes that failed

  • total: Total number of nodes attempted

Example: # Hide all cameras daz_batch_visibility(["Camera 1", "Camera 2", "Camera 3"], visible=False)

# Show multiple props
daz_batch_visibility(["Sword", "Shield", "Helmet"], visible=True)

# Hide environment elements for character close-up
daz_batch_visibility(["Ground", "Sky Dome", "Background"], visible=False)

Note: Hidden nodes are not visible in the viewport or renders, but remain in the scene. Use this for scene management, testing different configurations, or optimizing render times.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
node_labelsYes
visibleNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Tool Definition Quality

A4.4/5.0
Behavior4/5

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

No annotations provided, description carries full burden. It discloses that hidden nodes remain in scene, affects viewport and renders, and includes return structure. Missing details on undo behavior or batch size limits, but adequate.

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?

Well-structured with Args, Returns, Example, Note sections. Purpose is front-loaded. Slightly long but each section adds value. Could be more concise but still efficient.

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?

Covers purpose, parameters, returns, behavioral note, and examples. Output schema is described in text. No mention of permissions or prerequisites, but sufficient for most use cases.

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% (no descriptions in schema), but description fully explains both parameters: node_labels (list of labels) and visible (boolean, default true). Adds examples showing usage. Adds meaning beyond schema types.

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?

Description clearly states it shows or hides multiple nodes in viewport and renders. Verb+resource combination is specific and distinct from siblings like daz_batch_select 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?

Provides context on when to use (scene management, testing, render optimization) but does not explicitly state when not to use or compare to alternative tools like daz_batch_set_properties.

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