Skip to main content
Glama

ai_modeling_snapshot

Render a 3D model to a PNG with viewport modes, HDR environments, part expansion, and optional animation poses for preview or review.

Instructions

render a model PNG with viewport modes, HDR, part expansion and an optional animation pose

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_snapshot"
  }
}

Input Schema

NameRequiredDescriptionDefault
fovNoPerspective vertical field of view in degrees.
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.
azimuthNo
blenderNo
explodeNoSeparate mesh parts radially; 1 is fully expanded, without random spinning.
shadingNooriginal
skeletonNoOverlay projected joint connections from the evaluated pose.
animationNoExact embedded animation name or zero-based index; omit for the binding pose.
elevationNo
metalnessNo
roughnessNo
wireframeNo
model_pathYes
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
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.7/5.0
Behavior2/5

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

Annotations already declare the safety profile (readOnlyHint=false, destructiveHint=false, openWorldHint=true), and the description adds nothing on top: it does not say whether destination_path is overwritten, whether rendering is synchronous or expensive, or that network access happens for HDR presets. The genuinely useful behavioral caveats (PBR is a temporary switch, display modes are not pixel-identical to Studio, presets override the local three-light setup) live only in individual schema property descriptions, not in the tool description.

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?

A single front-loaded sentence with no filler, and the core artifact is stated first. Its economy is a virtue in isolation, though at 29 parameters the same length reads as under-specification rather than discipline.

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

Completeness2/5

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

For a 29-parameter rendering tool with no output schema and roughly half the parameters undocumented, one sentence is far too thin to let an agent invoke it correctly or predict cost and side effects. Nothing about return value, failure modes, or destination path handling is available anywhere.

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 29 parameters and only 55% schema description coverage, the description should carry real weight, but it merely names four feature areas (viewport modes, HDR, part expansion, animation pose) without explaining any parameter's semantics, ranges, or defaults. Several parameters with no schema description at all (size, azimuth, elevation, zoom, metalness, roughness, model_path, destination_path) get no coverage anywhere.

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?

"Render a model PNG" is a precise verb+artifact pair, and the trailing list (viewport modes, HDR, part expansion, animation pose) frames the scope of the output. It stops short of differentiating itself from the sibling snapshot tool ai_modeling_brush_snapshot, which an agent would also plausibly reach for when it wants an image of a model.

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?

The description states what the tool produces but never says when to choose it, what preconditions it needs (model path, resolved destination path, auth/account state), or when a different snapshot or export path is the better fit. No exclusions or alternatives are named.

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