Skip to main content
Glama
Sign In
Daz3D-MCP

Daz3D-MCP

by MictlanLabs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

anim_timeline

Read or set animation frame rate, playback range, and current frame, and list animated nodes with their frame ranges to inspect or adjust scene timing.

Instructions

Reads or sets the timeline: frame rate, animation range, current frame. Also lists which nodes are animated and over which frames.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "anim_timeline"
  }
}

Input Schema

NameRequiredDescriptionDefault
fpsNoNew frame rate (Daz default 30).
keepNoWith fps: duration keeps keys at their time in seconds; frames keeps them on their frame numbers (plays faster or slower).duration
frameNoGo to this frame (poses and presets apply here).
end_frameNoLast frame of the animation range.
start_frameNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

B3.4/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 safety profile is known. The description usefully discloses the dual read/write nature and the extra read-side behavior (reporting animated nodes and their frame spans), which goes beyond the annotations. It does not mention whether timeline edits are undoable or what happens to existing keys beyond what the 'keep' schema text covers.

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 tight sentences with the core verb and the affected fields front-loaded. The second sentence on animated-node listing earns its place by describing a distinct behavior. Slightly more could be trimmed or reordered, but there is no filler.

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 five-parameter mutating tool with no output schema, the description covers the input side adequately via the schema, and gestures at the return content by noting it lists animated nodes and their frame ranges. It stops short of describing the shape of that listing or any error/permission conditions, leaving a modest gap.

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?

With 80% schema description coverage, the schema already explains fps, keep, frame, start_frame and end_frame in detail. The description maps loosely onto those fields (frame rate, range, current frame) but adds no extra syntax, defaults or interaction detail, and never mentions the consequential 'keep' option.

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 states specific verbs and resources: it reads or sets frame rate, animation range and current frame, and it lists which nodes are animated over which frames. An agent can tell it is the timeline-level control rather than a keyframe or retime tool. It just doesn't name a sibling to differentiate against 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?

Usage is only implied by the "reads or sets" phrasing; there is no statement of when to prefer this over anim_retime, anim_keys_get or anim_keys_set. No prerequisites or when-not-to-use conditions are given, so the agent must infer selection from names alone.

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