Skip to main content
Glama
Sign In
Daz3D-MCP

Daz3D-MCP

by MictlanLabs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

anim_retime

Adjust animation timing by speeding up, slowing down, or matching a part to a set length; trailing keys follow to preserve sequence.

Instructions

Changes the rhythm of an animation: speeds it up, slows it down or fits it to a length. Keys after the part move with it.

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": "anim_retime"
  }
}

Input Schema

NameRequiredDescriptionDefault
nodeYesNode label.
snapNoKeep keys on whole frames.
speedNo2 = twice as fast, 0.5 = half speed.
lengthNoOr: frames the part should last.
end_frameNo
start_frameNoPart to retime; default the whole animation.
with_followersNoAlso retime clothing and hair keys.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare this is a non-destructive, non-readonly, closed-world mutation, so the description only needs to add context. "Keys after the part move with it" does add real value by disclosing that downstream keys shift, but nothing is said about reversibility, whether an undo point is created, or how snapping interacts with retiming.

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?

Two short sentences, front-loaded with the core action, and the downstream-keys caveat follows naturally. No filler, though a colon-list structure could have made the mode enumeration even tighter.

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 7-parameter mutation with no output schema, the description covers the primary behavior but omits how speed and length interact when both are supplied, and whether with_followers changes the effect on the downstream keys mentioned. The rich schema covers most of the rest, so this is adequate but not fully complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 86%, so the schema already documents speed ("2 = twice as fast"), length, snap, start/end frame, and with_followers. The description reinforces the speed-vs-length duality ("fits it to a length") and introduces the notion of a "part" that maps to start/end frame, but adds little beyond that.

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 names a specific verb and resource ("Changes the rhythm of an animation") and enumerates the three operating modes: speed up, slow down, fit to length. That is clearly distinct from siblings like anim_offset or anim_keys_set, though no sibling is named explicitly.

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?

The three modes imply when the tool is appropriate, and "Keys after the part move with it" hints at scope. But it never states when to pick speed vs length, whether they are mutually exclusive, or when to prefer anim_offset instead.

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