Skip to main content
Glama
Sign In
Daz3D-MCP

Daz3D-MCP

by MictlanLabs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

morph_list

Read-onlyIdempotent

List a figure's shape, pose, and face dials with values and ranges, then filter by label, name, or group to find morphs and marked controls.

Instructions

Lists the dials of a figure with their value and range: shape morphs and the figure's pose and face controls (Eye Blink, Jaw Open, Brow Up...; marked control=true).

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>"
    },
    "name": "morph_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
nodeYesFigure (or item) label.
limitNo
queryNoWords in the dial's label, name or group, e.g. 'height' or 'head'.
only_nonzeroNoOnly dials that are in use.
include_hiddenNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

B3.2/5.0
Behavior3/5

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

The annotations already establish this as a safe, idempotent, read-only, closed-world operation, so the safety burden is carried. The description adds useful data-model context (returned dials carry a value and a range, and control dials are marked control=true), but says nothing about pagination behavior, whether hidden dials dominate the result by default, or how limit interacts with the listing.

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?

A single front-loaded sentence with the verb and object up front. The parenthetical examples (Eye Blink, Jaw Open, Brow Up) and the control=true marker earn their place by clarifying what a 'control' dial is. Slight density from the nested parentheses keeps it from a 5.

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 read-only five-parameter listing tool with no output schema, annotations carry much of the burden and the description defines the returned item shape adequately. However, an agent still cannot tell from the definition whether the default call returns truncated results, whether hidden dials are excluded, or how to page through more than the default 100 dials.

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 coverage is 60%, so roughly two parameters (limit and include_hidden carry no description, and the description adds no meaning to query or only_nonzero either). The phrase 'with their value and range' is the only hint tied to filtering, and the marked control=true note is about output, not about how to filter input. The description does not compensate for the coverage gap.

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 opens with a specific verb and resource ('Lists the dials of a figure') and narrows the scope to shape morphs plus pose/face controls flagged control=true. An agent knows exactly what category of data comes back. It doesn't explicitly contrast itself with the morph_set sibling, so it falls short of a 5.

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: listing dials is naturally the discovery step before setting one, but the description never says so or names a companion tool. There is no when-not-to-use guidance and no mention of prerequisites such as needing a valid figure label.

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