Skip to main content
Glama

daz_render_with_camera

Render a scene from a specific camera without altering the viewport camera, enabling multi-camera batch renders.

Instructions

Render from specific camera without changing active viewport camera.

Renders the scene from the specified camera's viewpoint. The viewport camera remains unchanged, making this ideal for multi-camera renders without disrupting the user's viewport.

Args: camera_label: Display label of the camera to render from. output_path: Optional output file path. If not specified, renders to viewport.

Returns:

  • success: true on success

  • camera: camera label used for render

  • outputPath: output file path (or null if rendered to viewport)

Example: # Render from specific camera daz_render_with_camera("Camera 1", output_path="/path/to/render.png")

# Render from multiple cameras without changing viewport
cameras = ["Front", "Side", "Top", "Perspective"]
for cam in cameras:
    daz_render_with_camera(cam, output_path=f"renders/{cam}.png")

# Test render from camera (to viewport, no file)
daz_render_with_camera("Camera 1")

Note: - Viewport camera remains unchanged after render - Previous render camera is restored automatically - Use for multi-camera batch renders - Combine with daz_orbit_camera_around() to set up camera first

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
camera_labelYes
output_pathNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior5/5

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

Despite no annotations, the description fully discloses behavior: viewport remains unchanged, previous render camera is restored automatically, and return values are documented. It also mentions rendering to viewport when no output path is given.

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 for purpose, arguments, returns, example, and notes. Every sentence is informative and there is no wasted text.

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 the presence of an output schema, the description covers all essential aspects: purpose, parameters, return values, example usage, 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?

With 0% schema coverage, the description compensates fully: 'camera_label: Display label of the camera to render from.' and 'output_path: Optional output file path. If not specified, renders to viewport.' This adds meaning beyond the bare schema.

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's purpose: 'Render from specific camera without changing active viewport camera.' It uses a specific verb and resource, distinguishing it from siblings like daz_render and daz_set_active_camera.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicit guidance is given: 'ideal for multi-camera renders without disrupting the user's viewport.' The example shows batch rendering from multiple cameras, and the note suggests combining with daz_orbit_camera_around() for setup.

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