Skip to main content
Glama
Sign In
Daz3D-MCP

Daz3D-MCP

by MictlanLabs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

morph_set

Set shape morphs and pose or face dials on a Daz Studio figure or item by passing dial names and values; unknown dial names return similar matches for correction.

Instructions

Sets dials (shape morphs or pose/face controls), e.g. {"Body Tone": 0.5, "Eye Blink": 1}. Unknown dials come back with similar names.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "node": "<node>",
      "values": "<values>"
    },
    "name": "morph_set"
  }
}

Input Schema

NameRequiredDescriptionDefault
nodeYesFigure (or item) label.
valuesYes{dial label or name: value}, usually 0 to 1.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare this is a non-read-only, non-destructive, closed-world mutation, so safety framing is supplied. The description adds genuinely new behavior — unknown dial labels come back with near-matches rather than hard-failing — but omits the critical detail for a setter: whether dials not included in the values map are left untouched or reset.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, zero padding, with the primary action front-loaded before the example and the edge-case behavior placed last. Slightly clipped phrasing ('dials (shape morphs or pose/face controls)') costs a little readability but no space is wasted.

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?

Two required parameters and no output schema mean the description has limited ground to cover, and it covers the call correctly. However, for a mutation tool the merge-vs-overwrite semantics and the response content on partial name matches are left unstated, which an agent needs to call it safely.

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 coverage is 100%, with both 'node' (figure label) and 'values' (dial-to-number map, usually 0-1) already documented. The description's example reinforces the label-keyed map shape but contributes no additional format, range, or naming rules beyond the schema.

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 names a specific verb and resource ('Sets dials') and clarifies the resource with concrete types (shape morphs, pose/face controls) plus a literal example payload. An agent can tell this is the write-side counterpart to a dial listing tool, though it never names morph_list 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?

Usage is only implied: the note about unknown dials returning similar names hints that an agent should discover names (likely via morph_list) before setting, but neither the when-to-use condition nor the alternative tool is stated. No exclusions or prerequisites are given.

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