Skip to main content
Glama
HoldMyBeer-gg

blend-ai

by HoldMyBeer-gg
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

render_animation

Render the animation sequence to image files.

Instructions

Render the animation sequence to image files.

Args: filepath: Output file path prefix for the rendered frames. Each frame will be saved with a frame number suffix. The directory must exist. Empty means render_ in the system temp directory. format: Output format. One of: PNG, JPEG, OPEN_EXR, TIFF, BMP.

Returns: Confirmation dict with output details.

Input Schema

NameRequiredDescriptionDefault
formatNoPNG
filepathNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.3.0
    • changedInput schema / properties / filepath / default
      Previous value: -"/tmp/render_"New value: +""
  2. Changed2 schema fields changedv1.7.0
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / format / enum
      Added value: +[
+  "BMP",
+  "JPEG",
+  "OPEN_EXR",
+  "PNG",
+  "TIFF"
+]
  3. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It does disclose meaningful behavior: frames get numbered suffixes, an empty filepath defaults to 'render_' in the system temp dir, and the target directory must pre-exist. It omits whether the whole scene frame range is rendered, whether existing files are overwritten, and that this is a long-running operation.

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?

Front-loaded with the core action, then parameter details in a compact docstring layout. No filler sentences; the Args block is slightly verbose but each line carries a distinct constraint.

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?

An output schema exists, so 'Confirmation dict with output details' is acceptable. However, for a file-writing render operation with zero annotations, the definition should say more about scope (frame range) and overwrite/runtime behavior before an agent invokes it on a large scene.

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

Parameters4/5

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

Schema description coverage is 0%, but the description compensates well: it enumerates all valid formats and explains the filepath prefix, the frame-number suffix, the directory-existence requirement, and the empty-string default behavior that the schema's bare default of "" does not convey.

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?

States a specific verb and resource: 'Render the animation sequence to image files.' It is clear what the tool does, but it never distinguishes itself from the sibling render_image or render_video, which an agent choosing among three render tools would need.

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 implied (an animation is rendered to a frame sequence), and it helpfully warns that the output directory must exist. But there is no explicit guidance on when to pick this over render_video (single movie file) or render_image, nor any prerequisite note about frame range/camera setup.

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