Skip to main content
Glama
Sign In
Daz3D-MCP

Daz3D-MCP

by MictlanLabs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

wearable_adjust

Adjust clothing or hair fit by setting mesh smoothing and collision properties to stop skin poking through; omit arguments to report current values.

Instructions

Fixes how clothing sits on a figure: mesh smoothing and collision (cures skin poking through) and other item properties. Without arguments it reports the current values. For loose or tight fit dials use morph_list/morph_set on the item.

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": {
      "item": "<item>"
    },
    "name": "wearable_adjust"
  }
}

Input Schema

NameRequiredDescriptionDefault
itemYesClothing or hair label.
smoothingNo
propertiesNo{label: value} other properties of the item.
collide_withNoFigure to collide with; "" for none. Default: the figure it is fitted to.
collision_iterationsNoRaise it (3-10) when skin pokes through.
smoothing_iterationsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations declare non-destructive, non-open-world, non-read-only, and the description adds meaningful behavior on top: the same tool doubles as a reporter when no adjustment args are passed, and collision defaults to the figure the item is fitted to. It stops short of saying whether applied changes are undoable or persisted, which a mutating tool would ideally disclose.

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?

Three short sentences, front-loaded with purpose, then the read mode, then the sibling hand-off. Nothing is redundant and no sentence could be dropped without losing routing information.

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

Completeness4/5

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

For a 6-parameter mutation tool with no output schema, the definition covers purpose, dual read/write behavior, and the alternative tool. The remaining gaps are how smoothing vs collision interact and what the reporting mode returns, both minor given the schema's inline parameter docs.

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 67%, so most parameters are already documented (collide_with default, iteration ranges, properties as {label: value}). The description reinforces the smoothing/collision intent and the 'other properties' bucket but adds no syntax or interaction detail, and 'Without arguments' is slightly imprecise since 'item' is required.

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?

Names a concrete operation on a concrete resource: adjusting how clothing/hair sits on a figure via mesh smoothing and collision, with the user-visible symptom (skin poking through) spelled out. It also distinguishes itself from the morph dial tools, so an agent can pick this over 'loose/tight' adjustments without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit alternative route: 'For loose or tight fit dials use morph_list/morph_set on the item,' which is exactly the kind of routing an agent needs. It also states a distinct call mode ('Without arguments it reports the current values') plus the trigger condition for raising iterations in the schema text.

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