Skip to main content
Glama

daz_get_render_settings

Retrieve current render configuration from DAZ Studio, including render target, output path, aspect ratio, and render camera. Verify settings before batch rendering.

Instructions

Get current render settings and configuration.

Returns information about the current render configuration, including render target, output path, aspect ratio, and render camera.

Returns:

  • renderToFile: true if rendering to file, false if to viewport

  • outputPath: current output file path (or null)

  • currentCamera: label of current render camera (or null for viewport camera)

  • aspectRatio: aspect ratio value

  • aspectWidth: aspect width component

  • aspectHeight: aspect height component

Example: # Check render settings settings = daz_get_render_settings() print(f"Render camera: {settings['currentCamera']}") print(f"Output: {settings['outputPath']}") print(f"Aspect: {settings['aspectWidth']}x{settings['aspectHeight']}")

# Verify render is configured correctly before batch render
settings = daz_get_render_settings()
if not settings['renderToFile']:
    print("Warning: Render is configured for viewport, not file output")

Note: - Aspect ratio determines render dimensions relative to each other - Pixel dimensions cannot be set reliably via DazScript - currentCamera may be null if using active viewport camera

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

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 responsibility. It discloses the return format, lists all fields, and notes important behaviors (e.g., pixel dimensions cannot be set reliably, currentCamera may be null). This is thorough, though it could mention that it is a non-destructive read operation, which is implicit.

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 and well-structured: an overview sentence, a 'Returns' bullet list, an example, and a 'Note' section. Every section adds value without redundancy. It is front-loaded with the purpose.

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 that the tool has no parameters and an output schema exists, the description fully explains what the tool does, what it returns, and provides usage context. Limitations are noted, making it complete for an agent to invoke.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool has zero parameters, so schema coverage is trivially 100%. The description adds value by detailing the returned fields, which is beyond the input schema's scope. Baseline for no parameters is 4, and the description meets that.

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 'Get current render settings and configuration.' It uses a specific verb ('Get') and resource ('render settings'), and the returns section lists exactly what is retrieved. There is no ambiguity, and it distinguishes itself from sibling tools (e.g., daz_set_render_quality) by being a read-only query.

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

Usage Guidelines3/5

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

The description does not explicitly state when to use this tool versus alternatives. However, the example provides a practical usage scenario (checking settings before batch render), which implies its role. There is no mention of when not to use it or comparison to similar tools like daz_get_scene_info.

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