Skip to main content
Glama

daz_batch_render_cameras

Render a 3D scene from multiple camera angles in a single batch operation. Each camera generates a separate output file with the camera name appended to the base filename.

Instructions

Render from multiple cameras in sequence.

Renders the same scene from multiple camera angles in a single operation. Each camera generates a separate output file with the camera name appended.

Args: cameras: List of camera labels to render from. output_dir: Output directory for rendered images. base_filename: Base filename (default: "render"). Camera name is appended automatically.

Returns:

  • success: true on success

  • rendered: Array of {camera, outputPath} objects

  • total: Total number of cameras attempted

Example: # Render from multiple preset cameras daz_batch_render_cameras( cameras=["Front", "Side", "Top", "Perspective"], output_dir="/path/to/renders", base_filename="character" ) # Generates: character_Front.png, character_Side.png, etc.

# Render turntable (8 cameras around character)
cameras = [f"Cam_{angle}" for angle in [0, 45, 90, 135, 180, 225, 270, 315]]
daz_batch_render_cameras(cameras, "/path/to/turntable", "frame")

# Render all cameras in scene
scene_info = daz_scene_info()
all_cameras = [cam['label'] for cam in scene_info['cameras']]
daz_batch_render_cameras(all_cameras, "/path/to/renders")

Note: - Camera names in filenames have non-alphanumeric chars replaced with underscores - All renders use current scene state (same lighting, poses, etc.) - Previous render camera is restored after batch completes - Cameras that don't exist are skipped

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
camerasYes
output_dirYes
base_filenameNorender

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior5/5

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

With no annotations, the description fully discloses behavioral traits: file naming with underscore replacement, use of current scene state, restoration of previous camera, and skipping non-existent cameras. This is comprehensive.

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 sections (brief intro, Args, Returns, Example, Note). It is concise yet thorough, with every paragraph adding value.

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 complexity and presence of output schema, the description covers input parameters, return values, examples, and behavioral notes. It is complete for an agent to use correctly.

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 schema has 0% description coverage, but the description adds full meaning: cameras as list of labels, output_dir as directory, base_filename default with auto-appended camera name. 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 'Render from multiple cameras in sequence,' specifying the verb (render), resource (cameras), and scope (batch). It distinguishes from siblings like single-camera renders and async variants.

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 examples and notes on when to use the tool (multiple cameras) and behavior (skipping non-existent cameras). However, it does not explicitly state when not to use it compared to alternatives like single-camera renders, though the context is clear.

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