Skip to main content
Glama

daz_get_animation_info

Retrieve current animation timeline information including frame range, current frame, frames per second, total frames, and duration. Use this data to manage animation rendering or check playback position.

Instructions

Get animation timeline info (current frame, range, fps).

Returns information about the current animation timeline state, including the current frame, frame range, and frames per second.

Returns:

  • currentFrame: current timeline position

  • startFrame: first frame of animation range

  • endFrame: last frame of animation range

  • fps: frames per second

  • totalFrames: total number of frames (endFrame - startFrame + 1)

  • durationSeconds: animation duration in seconds

Example: # Get timeline info info = daz_get_animation_info() print(f"Current frame: {info['currentFrame']}") print(f"Range: {info['startFrame']}-{info['endFrame']}") print(f"Duration: {info['durationSeconds']} seconds") print(f"FPS: {info['fps']}")

# Render entire animation
info = daz_get_animation_info()
for frame in range(info['startFrame'], info['endFrame'] + 1):
    daz_set_frame(frame)
    daz_render(output_path=f"output/frame_{frame:04d}.png")

# Check if at end of animation
info = daz_get_animation_info()
if info['currentFrame'] >= info['endFrame']:
    print("At end of animation")

Note: - FPS is typically 30 in DAZ Studio - Frame range is inclusive (both start and end are included) - totalFrames includes both start and end frames - Use before rendering animation to know frame count

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior5/5

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

With no annotations, the description fully discloses the tool's behavior as a read-only retrieval of animation timeline information. It details all return fields, including the calculation of totalFrames and durationSeconds, and notes that FPS is typically 30. No side effects or destructive actions are implied.

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?

The description is well-structured and front-loaded with a one-line summary, followed by a list of return values, practical examples, and concise notes. Every sentence adds essential information without redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given that there are no parameters and an output schema exists, the description is complete. It covers all aspects of the tool's purpose, return values, and usage context, including edge cases like the inclusive frame range and typical FPS. The examples also demonstrate integration with other tools.

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

Parameters5/5

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

The tool has no parameters, so the baseline is 4. The description adds value by explaining each return field in detail (e.g., totalFrames = endFrame - startFrame + 1, durationSeconds calculation) and provides examples that demonstrate usage. This goes beyond what the empty schema provides.

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?

The description clearly states 'Get animation timeline info (current frame, range, fps)', which is a specific verb+resource. It distinguishes from sibling tools like daz_set_frame (which sets a frame) and daz_render_animation (which renders), as it focuses solely on retrieving timeline state.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explicitly advises to use it 'before rendering animation to know frame count' and provides examples for iterating over frames, checking the end of animation, and getting duration. It clarifies typical FPS and the inclusive nature of the frame range, giving clear context for when and how to use it.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/bluemoonfoundry/daz-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server