Skip to main content
Glama
Sign In
Daz3D-MCP

Daz3D-MCP

by MictlanLabs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

pose_bones

Rotates figure bones to adjust poses after applying a preset or build poses from scratch, and reports dials clamped at Daz joint limits.

Instructions

Rotates figure bones, for adjustments after a pose preset or to build a pose. Reports dials that Daz held at a joint limit.

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": {
      "figure": "<figure>",
      "bones": "<bones>"
    },
    "name": "pose_bones"
  }
}

Input Schema

NameRequiredDescriptionDefault
bonesYes{bone name: [x, y, z] degrees}, e.g. {"l_upperarm": [0, 0, -40]}.
figureYesFigure label.
relativeNoAdd to the current rotation.
ignore_limitsNoTurn off these bones' joint limits first. Daz clamps dials to the limits; the result lists clamped values.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A4/5.0
Behavior4/5

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

Annotations only declare the safety profile (not read-only, not destructive, closed-world), so the description carries the remaining burden well by disclosing the return behavior: it reports dials Daz held at a joint limit. That detail is essential for interpreting output and is not derivable from the annotations. It stops short of describing persistence or undo characteristics of the rotation.

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 short sentences, verb and resource front-loaded, with the secondary reporting behavior placed after the primary purpose. No filler wording or redundant restatement of the tool name.

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 mutation tool with no output schema, the description supplies a return-value hint (clamped dial reports) that an agent would otherwise lack, and the schema already covers all parameters. Slightly more on whether the rotation persists or requires a subsequent key/save step would round it out.

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 four parameters (bones, figure, relative, ignore_limits) are already documented in the schema with defaults and an example. The description's mention of reported clamped dials adds a little meaning to ignore_limits, but nothing about the rotation semantics or bone-name format 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 gives a specific verb ('Rotates') and resource ('figure bones'), plus a second sentence on what it reports back. It does not explicitly name a sibling such as pose_reset or anim_preset_apply, so differentiation is implied through the 'after a pose preset' phrasing rather than stated.

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

Usage Guidelines4/5

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

It provides clear context for when to reach for it: fine adjustment after applying a pose preset, or building a pose from scratch. It does not state exclusions or name an alternative tool for the 'start from a preset' or 'reset' cases, leaving selection to inference.

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