Skip to main content
Glama

daz_set_render_quality

Adjust Iray render quality preset to trade speed for quality. Choose from draft, preview, good, or final for quick composition checks or production renders.

Instructions

Set the Iray render quality preset.

Adjusts Max Samples and Render Quality on the active renderer, trading speed for quality. Use "draft" for quick composition checks and "final" for production renders.

Presets: draft - Very fast (seconds–2 min). Low quality. For quick checks. preview - Fast (2–5 min). Moderate quality. For composition review. good - Slow (10–20 min). Good quality. For client review. final - Very slow (30 min–2 hr). Maximum quality. For final output.

Args: preset: One of "draft", "preview", "good", "final".

Returns: { "preset": "draft", "propertiesSet": [ {"property": "Max Samples", "value": 100}, {"property": "Render Quality", "value": 0.5} ], "note": "..." # present only if some properties were not found }

Example: # Quick test render daz_set_render_quality("draft") daz_render("/test.png")

# Final quality async render
daz_set_render_quality("final")
req = await daz_render_async("/final.png")
result = await daz_get_request_result(req["request_id"], wait=True)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
presetYes

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 fully explains that the tool modifies render quality and max samples, returns properties set, and provides a note if some properties are missing. It also implies speed trade-offs via preset descriptions. However, it does not mention prerequisites like an open scene or active renderer, nor effects on ongoing renders.

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-organized into sections: a one-line purpose, a preset table, args, returns, and an example. Every sentence is informative, with no fluff or repetition. The structure makes it easy to scan.

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 low complexity (single parameter, presets) and the presence of an output schema, the description fully covers behavior, input options, return format, and practical usage via examples. Nothing essential is missing.

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 only defines 'preset' as a required string with 0% description coverage. The tool description compensates thoroughly by listing each preset value with typical time ranges and quality levels, adding significant meaning beyond the schema's minimal 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 'Set the Iray render quality preset' and explains it adjusts Max Samples and Render Quality. It unambiguously identifies the tool's function and distinguishes it from siblings like render tools or property setters.

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 explicit guidance on when to use each preset ('Use "draft" for quick composition checks and "final" for production renders') and includes an example with two contexts. It does not explicitly state when not to use the tool or mention alternatives, but the context is clear enough for typical scenarios.

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