Skip to main content
Glama

daz_set_frame_range

Set the start and end frames of the animation timeline to define the playback and export range.

Instructions

Set animation frame range (start and end).

Defines the playback range for the animation timeline. This determines which frames are included when playing or exporting animation.

Args: start_frame: First frame of animation (typically 0). end_frame: Last frame of animation.

Returns:

  • success: true

  • startFrame: new start frame

  • endFrame: new end frame

  • previousStart: previous start frame

  • previousEnd: previous end frame

Example: # Set 120-frame animation (4 seconds at 30fps) daz_set_frame_range(0, 119)

# Set 300-frame animation (10 seconds at 30fps)
daz_set_frame_range(0, 299)

# Set custom range starting from frame 10
daz_set_frame_range(10, 100)

Note: - Frame range is inclusive (both start and end frames are included) - Default FPS in DAZ Studio is typically 30 - Duration in seconds = (end - start + 1) / fps - Example: frames 0-29 at 30fps = 1 second (30 frames)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
start_frameYes
end_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, but the description fully discloses behavioral traits: sets start/end frames, inclusive, default FPS, duration calculation, and returns previous and new values. No contradictions.

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?

Well-organized with sections (Args, Returns, Example, Note). Front-loaded with purpose. Slight verbosity in the note but overall efficient. Deserves a 4 for good structure.

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 no annotations and 0% schema coverage, the description is complete. It covers return values, inclusive range, FPS, and duration formula. No gaps for the agent to infer.

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 no descriptions, but the description explains each parameter (start_frame as first frame, end_frame as last frame) and provides examples. Adds significant meaning beyond the schema.

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?

Clearly states 'Set animation frame range' with specific verb and resource. The description distinguishes this from sibling tools like 'daz_set_frame' (current frame) and 'daz_clear_animation'. The purpose is unambiguous.

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?

Implied usage is clear: for setting the playback range of animation. Provides context about inclusive range and FPS, but doesn't explicitly state when not to use or compare to alternatives. Still, the context is sufficient for an AI agent to infer appropriate use.

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