Skip to main content
Glama
Sign In
Daz3D-MCP

Daz3D-MCP

by MictlanLabs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

anim_preset_save

Save a figure's animation as a reusable preset in ~/.daz3d-mcp/animations so you can apply it later to any figure of the same generation.

Instructions

Saves a figure's animation as a reusable preset (~/.daz3d-mcp/animations), to apply later to any figure of the same generation with anim_preset_apply.

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

Input Schema

NameRequiredDescriptionDefault
loopNoIt is a cycle: the last frame matches the first, and repeats carry on walking from where the last cycle ended.
nameYesPreset name, e.g. 'walk-cycle-relaxed'.
figureYesFigure whose animation to save.
morphsNoInclude animated dials (expressions).
end_frameNoDefault: the last key.
overwriteNo
with_nodeNoInclude the figure's own position and rotation keys.
descriptionNo
start_frameNoDefault: the first key.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare a non-read-only, non-destructive, closed-world operation, so the bar is lower; the description contributes the on-disk destination (~/.daz3d-mcp/animations) and the cross-figure generation constraint. It says nothing about name-collision behavior despite the schema's overwrite flag defaulting to false, which is the key risk an agent needs to understand before saving.

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?

A single sentence that front-loads the action, the artifact, and its persistence path, then closes with the downstream tool. No redundant or filler wording.

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 9-parameter mutation tool with no output schema, the description covers purpose and destination but leaves the result (what is returned or written) and overwrite/failure behavior implicit. Sufficient to select the tool, but thin for invoking it confidently with non-default flags.

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 78%, near the high threshold, so the schema largely documents parameters (loop, morphs, node/keys, frame bounds, overwrite). The description adds no parameter-level meaning beyond that, which is acceptable at this coverage level but not additive.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a concrete verb and resource ('Saves a figure's animation as a reusable preset'), names the storage location, and explicitly distinguishes itself from the sibling that consumes the preset (anim_preset_apply). An agent knows exactly what this does relative to other anim_preset_* tools.

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?

Gives clear usage context via the 'to apply later to any figure of the same generation with anim_preset_apply' clause, which tells the agent both the downstream consumer and the compatibility restriction. It stops short of stating when not to save (e.g., no animation on the figure) or how it relates to anim_preset_list, so it is strong but not exhaustive.

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