Skip to main content
Glama

cinematic_render

Transform simulation files into publication-quality 3D images with auto-framing, cinematic lighting, and adjustable rendering presets.

Instructions

Cinematic-quality rendering with auto-framing, 3-point lighting, SSAO, and PBR.

Produces publication/presentation-quality images with:

  • PCA-based auto-camera: analyzes object shape and picks optimal viewing angle

  • 3-point cinematic lighting (key + fill + rim)

  • SSAO (Screen-Space Ambient Occlusion) for contact shadows

  • FXAA anti-aliasing

  • Gradient backgrounds

  • PBR material support (metallic/roughness)

Quality presets:

  • draft: 960x540, no post-processing (fast preview)

  • standard: 1920x1080, SSAO + FXAA

  • cinematic: 1920x1080, all effects + ground plane

  • ultra: 3840x2160, all effects + ground plane

  • publication: 2400x1800, clean lighting, white background

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
file_pathYesPath to simulation file
field_nameNoField to visualize (None for auto-detect)
colormapNoColor map preset (e.g., "Cool to Warm", "Viridis")Cool to Warm
qualityNoRendering quality presetstandard
lightingNoLighting preset (cinematic, dramatic, studio, publication, outdoor, None)cinematic
backgroundNoBackground preset (dark_gradient, light_gradient, blue_gradient, publication, None)dark_gradient
azimuthNoCamera azimuth in degrees (None for auto from shape analysis)
elevationNoCamera elevation in degrees (None for auto from shape analysis)
fill_ratioNoHow much of viewport the object fills (0.0-1.0, default 0.75)
metallicNoPBR metallic factor (0.0-1.0)
roughnessNoPBR roughness factor (0.0-1.0)
ground_planeNoAdd a semi-transparent ground plane for shadow catching
ssaoNoEnable Screen-Space Ambient Occlusion
fxaaNoEnable Fast Approximate Anti-Aliasing
widthNoOverride image width (None uses quality preset)
heightNoOverride image height (None uses quality preset)
scalar_rangeNo[min, max] for color scale, None for auto
timestepNoSpecific timestep, "latest", or None for first
output_filenameNoOutput PNG filenamecinematic.png
Behavior4/5

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

With no annotations, the description carries full burden and details auto-camera behavior (PCA-based), lighting and effect options, and quality presets. It does not mention potential side effects (e.g., file overwrite) or performance implications, but the disclosed behavior is comprehensive for a rendering tool.

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?

The description is front-loaded with the main purpose, then bullet-points features and quality presets. Every sentence contributes meaning, and it is appropriately sized for a tool with many parameters.

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?

Given 19 parameters and no output schema, the description covers rendering features and presets well but omits what the tool returns (e.g., the saved file path or status). It assumes an output file is written, but this is not explicitly stated.

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 coverage is 100% with all parameters described, so description adds value by explaining auto-camera behavior for azimuth/elevation and listing quality presets with specific resolutions/effects. This contextualizes the enumeration of the 'quality' parameter 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?

The description clearly states the tool does 'cinematic-quality rendering' with specifics like auto-framing, 3-point lighting, SSAO, and PBR. It distinguishes itself from siblings such as 'render' and 'volume_render' by emphasizing publication/presentation quality.

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?

The description implies usage for high-quality renders via quality presets but does not explicitly state when to use this tool over alternatives like 'render' or 'preview_3d'. No when-not-to-use or exclusion criteria are provided.

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/kimimgo/viznoir'

If you have feedback or need assistance with the MCP directory API, please join our Discord server