Skip to main content
Glama

ai_modeling_showcase_video

Render Showcase Dark or Showcase Sweep MP4 videos of 3D models locally using Blender and FFmpeg, with camera, lighting, shading, and animation controls.

Instructions

render Showcase Dark or Showcase Sweep MP4 locally with Blender and FFmpeg

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "model_path": "<model_path>",
      "destination_path": "<destination_path>"
    },
    "name": "ai_modeling_showcase_video"
  }
}

Input Schema

NameRequiredDescriptionDefault
fovNoPerspective vertical field of view in degrees.
fpsNo
pbrNoTemporary PBR switch; does not change source materials.
gridNoShow a ground grid in the preview.
sizeNo
zoomNoMagnification relative to the fitted camera.
pan_xNoHorizontal camera pan as a fraction of the fitted view width.
pan_yNoVertical camera pan as a fraction of the fitted view height.
ffmpegNo
azimuthNo
blenderNo
explodeNoSeparate mesh parts radially; 1 is fully expanded, without random spinning.
shadingNooriginal
durationNo
skeletonNoOverlay projected joint connections from the evaluated pose.
templateNoshowcase-dark
animationNoExact embedded animation name or zero-based index; omit for the binding pose.
elevationNo
metalnessNo
roughnessNo
wireframeNo
model_pathYes
project_idNoOptional project QR; does not change visibility.
projectionNoorthographic
environmentNoFetch a public Studio HDR preset at runtime; overrides the local three-light setup.
display_modeNoLocal equivalents of Studio viewport modes; not pixel-identical shaders.material
camera_motionNoturntable
animation_loopNoLoop the clip, or hold its last pose when false.
animation_timeNoSeconds from the selected clip start.
animation_speedNo
destination_pathYes
environment_pathNoCaller-provided Radiance HDR file instead of a preset.
environment_rotationNoEnvironment rotation in degrees around the vertical axis.
environment_intensityNo
environment_auto_rotateNoRotate HDR by 0.5 radians per second during video, matching Studio.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.4

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and openWorldHint=true, so the write/open-world profile is covered. The description adds genuinely new context by stating the render happens locally via Blender and FFmpeg, which implies external binary dependencies and local filesystem writes to destination_path. It does not disclose blocking behavior, runtime duration, failure modes, or that environment presets are fetched at runtime.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The single sentence is front-loaded and free of filler, so nothing is wasted. But for a 35-parameter rendering tool with a low-coverage schema, this brevity is under-specification rather than conciseness, and the sentence carries no structural aids such as prerequisites or defaults.

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 complex local render pipeline with 35 inputs, no output schema, and only 49% parameter coverage, the description is too thin to be complete. It does at least convey the output artifact (MP4), the local toolchain, and the two templates, which is the minimum an agent needs to attempt a call.

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

Parameters2/5

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

With 35 parameters at 49% schema coverage, roughly half the inputs are documented nowhere, and the description supplies almost no compensating meaning. It only implicitly signals that the template parameter accepts two named values and that the blender/ffmpeg parameters are likely executable paths; it says nothing about the camera, environment, animation, or display-mode controls.

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 names a specific verb (render) and a concrete resource (an MP4 of one of two named showcase templates), and it correctly identifies the two template values that also appear in the schema enum. It stops short of differentiating this tool from any sibling or explaining what distinguishes Showcase Dark from Showcase Sweep, so it is clear but not fully self-locating.

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

Usage Guidelines2/5

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

There is no guidance on when to choose this render path versus other generation or preview tools, nor any stated prerequisites despite the description implying external Blender and FFmpeg dependencies. An agent gets no exclusions, no cost/time expectations, and no indication of what to do if the local binaries are absent.

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