Skip to main content
Glama

daz_batch_render_cameras_async

Queue renders from multiple cameras as separate async requests, enabling independent cancellation and progress tracking for each camera angle.

Instructions

Queue renders from multiple cameras — each becomes its own async request.

Submits one async render per camera and returns all request IDs immediately. Renders execute serially (DAZ is single-threaded), so they queue behind any already-running request. Each camera render is independently cancellable.

Args: cameras: List of camera display labels. output_dir: Directory where rendered images are saved. base_filename: Filename prefix. Output is _.png.

Returns: { "request_ids": ["script-XXXXXXXX", ...], "total": 3, "cameras": ["Cam_0", "Cam_45", "Cam_90"] }

Example: batch = await daz_batch_render_cameras_async( cameras=["Cam_0", "Cam_45", "Cam_90"], output_dir="/renders/turntable" ) # Monitor all renders for req_id in batch["request_ids"]: result = await daz_get_request_result(req_id, wait=True)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
camerasYes
output_dirYes
base_filenameNorender

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 discloses that renders execute serially due to DAZ being single-threaded, queuing behind running requests, and that each render is independently cancellable. It does not mention file overwrite behavior or prerequisites, but the disclosed traits are sufficient for typical use.

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 a one-line summary, behavioral details, clearly labeled Args/Returns sections, and a complete example. Every sentence adds value without redundancy.

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?

Given the lack of annotations and output schema not shown, the description covers behavior, parameters, and return structure comprehensively. It could mention error cases or prerequisites (e.g., camera labels must exist), but the provided details are sufficient for correct invocation.

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 has 0% description coverage, but the description fully explains each parameter: cameras as 'List of camera display labels.', output_dir as 'Directory where rendered images are saved.', and base_filename with the naming pattern. The example reinforces 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 the tool queues renders from multiple cameras into individual async requests. It distinguishes itself from siblings like daz_batch_render_cameras (likely synchronous) and other single-camera render tools by highlighting async behavior and multi-camera capability.

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 when to use the tool (multiple camera renders asynchronously) and provides an example of monitoring renders with daz_get_request_result. However, it does not explicitly state when not to use it or compare to alternatives like daz_render_async or daz_batch_render_cameras.

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