Skip to main content
Glama

daz_set_frame

Set the current animation frame to evaluate and display the scene state at that frame. Use to navigate timeline, inspect keyframes, or prepare for rendering.

Instructions

Set current animation frame.

Moves the timeline to the specified frame. This updates the scene to show the state at that frame, evaluating all animated properties.

Args: frame: Frame number to move to (integer).

Returns:

  • success: true

  • frame: new current frame

  • previousFrame: frame number before the change

Example: # Jump to specific frame daz_set_frame(30)

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

# Preview keyframes
keyframes = daz_get_keyframes("Genesis 9", "XTranslate")
for kf in keyframes['keyframes']:
    daz_set_frame(kf['frame'])
    # ... preview or inspect ...

Note: - Scene updates to show animated state at the frame - All animated properties evaluate at the new frame - Frame numbers are typically 0-based integers - Use with daz_render() to export animation frames

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
frameYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior5/5

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

No annotations provided, so description carries full burden. It discloses that the scene updates to show animated state, evaluates all animated properties, and returns success, frame, and previousFrame. Side effects are clearly documented.

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?

Well-structured with a one-line summary, detailed paragraph, Args/Returns/Example/Note sections. Every sentence adds value, and the front-loaded summary aids quick understanding.

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 one parameter and an output schema, the description covers behavior, side effects, examples, and notes. It is fully complete for an agent to select and invoke correctly.

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?

Schema has only one parameter with 0% coverage, but description compensates by documenting 'frame' as integer, explaining it sets the frame number, and providing examples. No additional meaning needed.

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 the tool sets the current animation frame, moves the timeline, and updates the scene. It uses specific verbs and resources, distinguishing from siblings like daz_set_frame_range and daz_get_animation_info.

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?

Provides context for usage with examples (rendering animation, previewing keyframes) and notes about frame numbers. However, lacks explicit guidance on when not to use this tool or alternatives.

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