Skip to main content
Glama
Sign In
Daz3D-MCP

Daz3D-MCP

by MictlanLabs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

anim_key_pose

Keys a figure's current pose at specified frames, turning pose presets or bone edits into animation key poses.

Instructions

Keys the figure's current pose at frames: after a pose preset or pose_bones, this turns the pose into a key pose of the animation.

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

Input Schema

NameRequiredDescriptionDefault
figureYesFigure label.
framesYesFrames to key the current pose at.
morphsNoAlso key these dials (expressions).
all_bonesNoKey every bone (default: posed or animated ones and the hip).
with_nodeNoAlso key the figure's position and rotation.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A3.6/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 agent knows this is a bounded write. The description adds the important behavioral fact that the tool reads live state (the figure's current pose) rather than accepting pose data. It does not say what happens to keys already present at those frames (overwrite vs. insert), which is the main behavioral unknown for a keying tool.

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 dense sentence with the verb and object front-loaded and the workflow dependency second. No filler or repetition. Punctuation (colon plus trailing sentence) is slightly awkward but does not impede parsing.

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?

With five fully documented parameters, present annotations, and no output schema to explain, the description supplies the workflow sequencing that the schema cannot. The remaining gap — behavior on pre-existing keys at the same frames — is real but narrow for a keying operation.

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 five parameters including morphs, all_bones, and with_node are already documented in structured form. The description adds only the state-dependency framing and the implied scope of 'frames', which is modest value beyond the schema. Baseline 3 is appropriate.

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?

States a concrete verb and resource: it keys the figure's current pose at specified frames, converting a live pose into an animation key pose. The workflow hint (after a pose preset or pose_bones) implies it is distinct from pose_bones and pose_reset, but it never names the nearest sibling (anim_keys_set) that an agent might confuse it with.

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?

Explicitly gives the precondition for use: first apply a pose preset or call pose_bones, then key the result. That is clear when-to-use context. It stops short of exclusions — e.g., what to do if you want to key arbitrary values rather than the current pose, or how this differs from anim_keys_set on existing keys.

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