Skip to main content
Glama

daz_render_async

Initiate a DAZ Studio render in the background and retrieve the result later. Submit a render task, receive a request ID, and poll for progress without blocking scene operations.

Instructions

Start a render asynchronously — returns immediately with a request_id.

Use daz_get_request_status() to poll progress and daz_get_request_result() to retrieve the final result.

IMPORTANT: The scene is locked while the render runs. Do not modify the scene until the request status is "completed", "failed", or "cancelled".

Args: output_path: Optional file path for the rendered image.

Returns: {"request_id": "script-XXXXXXXX", "status": "queued", "submitted_at": "..."}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
output_pathNo

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 does a good job explaining the async nature, immediate return, scene locking, and the return value structure. Lacks details about resource usage or cancellation behavior.

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, front-loaded with the main purpose, and uses a structured format with Args and Returns sections. Every sentence adds value.

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 the core functionality well given the simple async nature. Could mention default behavior when output_path is omitted or any prerequisites like scene load.

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 single parameter 'output_path' is explained as an optional file path for the rendered image, adding meaning beyond the schema's generic type definition.

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 starts a render asynchronously and returns immediately with a request_id. It distinguishes from synchronous renders and other async variants like daz_render_animation_async.

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?

It specifies that the scene is locked during render and advises not to modify until completion. It also references sibling tools for polling and result retrieval. It could be more explicit about when not to use this tool (e.g., if synchronous behavior is desired).

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