Skip to main content
Glama
Sign In
Daz3D-MCP

Daz3D-MCP

by MictlanLabs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

environment_set

Configures the Iray environment by setting dome light, HDRI, and sun-sky options, or reports current settings when called without arguments.

Instructions

Sets the Iray environment (dome light, HDRI, sun-sky). Without arguments it reports it.

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": "environment_set"
  }
}

Input Schema

NameRequiredDescriptionDefault
hdriNoAbsolute path of an .hdr/.exr image; "" removes it.
modeNoscene_only turns the dome off so only scene lights count.
rotationNoDome rotation, degrees.
draw_domeNoShow the HDRI as the background.
intensityNoDome strength, 1 = default.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A3.5/5.0
Behavior3/5

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

The annotations already indicate a non-read-only, non-destructive, closed-world mutation. The description adds useful context that calling without arguments reports the environment state, but it does not explain whether omitted parameters are left unchanged, whether the call is idempotent, or how existing environment settings are affected.

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 two short sentences with no wasted wording. The core mutation purpose is front-loaded and the no-argument reporting behavior follows immediately.

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 five-parameter setter with no output schema, the description covers the main purpose and the special no-argument reporting mode. However, it omits important behavioral detail about how partial updates are handled and what the no-argument report contains, leaving meaningful gaps for correct invocation.

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

Parameters3/5

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

Schema description coverage is 100%, so all five optional parameters are already well documented in the input schema. The description does not add parameter-level semantics beyond what the schema provides, which is the baseline case for fully covered schemas.

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?

The description states a specific verb and resource: sets the Iray environment, including dome light, HDRI, and sun-sky. It clearly distinguishes the tool from generic lighting or camera setters by naming the environment subsystem, though it does not explicitly contrast with a sibling like light_set.

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?

Usage is implied by the tool name and description: use it to configure the Iray environment. The no-argument reporting behavior is disclosed, but there is no explicit guidance on when to prefer this over light_set, camera_set, or other environment-related alternatives, nor any stated exclusions.

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