Skip to main content
Glama
Sign In
Daz3D-MCP

Daz3D-MCP

by MictlanLabs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

render

Render the current Daz Studio scene with Iray and get the finished image back, with optional time or sample limits so test renders finish quickly.

Instructions

Renders the scene with the current renderer (Iray), waits until it is done and returns the image. Set max_time or max_samples so a test render does not run for long.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "render"
  }
}

Input Schema

NameRequiredDescriptionDefault
frameNoTimeline frame to render; default the current one.
widthNo
cameraNoCamera label; default is the active one.
heightNo
qualityNo
max_timeNoStop after this many seconds.
out_pathNoAbsolute .png or .jpg path; default ~/.daz3d-mcp/renders/.
overwriteNo
max_samplesNo
preview_sizeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A3.5/5.0
Behavior4/5

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

Annotations only declare the non-read-only, non-destructive, non-open-world profile; the description adds the critical fact that the call blocks until the render completes and that render duration is controlled by max_time/max_samples. It does not cover overwrite semantics or what happens to prior files, but the blocking/timeout behavior is meaningful context beyond the annotations.

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?

Two sentences, zero waste: the purpose and blocking behavior lead, followed by the operational caution. Nothing is repeated or padded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 10-parameter, blocking, image-producing tool with no output schema, the description covers the core action and timeout control but omits what the return value looks like, how overwrite interacts with out_path, and what quality/preview_size do. Adequate but with clear gaps for an agent invoking it correctly on the first try.

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

Parameters2/5

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

Schema description coverage is only 40% across 10 parameters, and the description only references max_time and max_samples, both of which are already documented in the schema. Width, height, quality, overwrite, and preview_size receive no meaning from the description, so it fails to compensate for the low coverage.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Renders the scene'), names the renderer (Iray), and clarifies the interaction model ('waits until it is done and returns the image'). It implicitly separates itself from render_animation by producing a single image, though it never names that sibling explicitly.

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 second sentence gives practical usage advice ('Set max_time or max_samples so a test render does not run for long'), which steers test-render scenarios. However, there is no explicit guidance on when to choose this over render_animation or render_shots, so the routing guidance is only implied.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools