Skip to main content
Glama
Sign In
Daz3D-MCP

Daz3D-MCP

by MictlanLabs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

anim_offset

Relocates an animation in time and space by shifting frames, moving or turning its path, or setting a new start point without changing the motion itself.

Instructions

Relocates an animation: in time (later or earlier) and in space (move it, turn its path, or make it start at a spot). The motion itself does not change.

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_offset"
  }
}

Input Schema

NameRequiredDescriptionDefault
moveNoCarry the whole motion by [x, y, z] cm.
nodeYesNode label.
turnNoTurn the whole motion (its path too) by degrees around Y.
framesNoStart it this many frames later (negative: earlier).
start_atNo[x, z] cm where the figure's hip should be at the first key.
with_followersNoWith frames: shift clothing and hair keys too.

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 this is a non-read-only, non-destructive, closed-world mutation. The description adds a meaningful behavioral guarantee — 'the motion itself does not change' — which tells the agent the edit is a pure transform of existing keys rather than a re-authored motion. It stops short of saying whether keys are modified in place, whether unspecified offsets mean no change, or what is returned.

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, front-loaded with the operation, then the two axes, then the invariant. No filler, and the parentheticals carry real information rather than restating the 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 six-parameter transform with a fully documented schema, the description covers the conceptual model and the key invariant an agent needs before calling it. Minor gaps remain — no mention of how with_followers behaves or that offsets are additive to existing keys — but these are largely covered by the schema.

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 every one of the six parameters is already documented in the schema, including units (cm, degrees, frames) and the negative-frames convention. The description's prose mirrors those same concepts ('later or earlier', 'move it', 'turn its path', 'start at a spot') without adding new semantics such as how frames and start_at interact. Baseline 3 applies.

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 ('Relocates an animation') and enumerates the two axes it operates on: time (later/earlier) and space (move, turn, or reposition start). That distinguishes it reasonably from a retiming or key-editing sibling, though no sibling is named.

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?

Usage is implied by the described capability — an agent can infer to use this when it wants to shift an animation without altering the motion itself. However, there is no explicit 'use this instead of anim_retime when…' or stated precondition, so the agent must infer the boundary with alternatives.

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