Skip to main content
Glama
Sign In
Daz3D-MCP

Daz3D-MCP

by MictlanLabs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

pose_reset

Restores all bones of a specified figure to the default pose, clearing custom posing so the character returns to its neutral stance before rebuilding a new pose.

Instructions

Returns all the bones of a figure to the default pose.

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

Input Schema

NameRequiredDescriptionDefault
figureYesFigure label.

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?

Annotations already declare readOnlyHint=false and destructiveHint=false, so the write-safety profile is covered and the description does not contradict it: resetting to default is consistent with a non-destructive write. The description usefully adds that ALL bones are affected, but says nothing about whether keyframed poses survive, whether the operation is undoable, or what happens if the figure is not currently posed.

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 no filler; the scope word "all" is placed where it matters. It is arguably too terse for a mutation tool, but no sentence 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?

For a one-parameter tool with annotations present and no output schema, the definition covers the essentials — action, target, and scope. However, it omits interaction with animation data (keyframes, presets) and failure conditions, which an agent invoking a pose-mutating tool would reasonably want.

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?

Only one parameter exists and the schema already documents it at 100% coverage ("Figure label"), so the baseline is 3. The description adds nothing about the figure parameter — e.g., whether it must be the active/selected figure or accepts any label.

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?

"Returns all the bones of a figure to the default pose" names a specific action (reset) and a specific resource (all bones of a figure), and the scope word "all" makes clear it is not a per-bone operation like pose_bones. It stops short of naming a sibling it is contrasted with, so it does not fully earn 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 Guidelines2/5

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

There is no explicit guidance on when to use this versus pose_bones or anim_key_pose, and no statement of prerequisites. The reset semantics imply an undo/cleanup use case, but the agent must infer that entirely.

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