Skip to main content
Glama

render

Visualize a field from a 3D simulation file and export the view as a PNG screenshot with customizable colormap, camera angle, resolution, and timestep.

Instructions

Render a field visualization and return a PNG screenshot.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
file_pathYesPath to simulation file
field_nameYesName of the field to visualize (e.g., "p", "U", "T")
associationNo"POINTS" or "CELLS"POINTS
colormapNoColor map preset (e.g., "Cool to Warm", "Viridis", "Jet")Cool to Warm
cameraNoCamera preset — isometric, top, front, right, left, backisometric
scalar_rangeNo[min, max] for color scale, None for auto
purposeNoResolution preset — "analyze" (480p), "preview" (720p), "publish" (1080p)analyze
widthNoOverride width in pixels (must set both width and height, or neither)
heightNoOverride height in pixels (must set both width and height, or neither)
timestepNoSpecific timestep, "latest", or None for first
blocksNoMultiblock region names to include
output_filenameNoOutput PNG filename (e.g., "snapshot_press.png")render.png
Behavior3/5

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

No annotations are provided, so the description carries full behavioral disclosure burden. It correctly states the return type (PNG screenshot) but does not mention that the tool is read-only or that it requires no file modifications. The description is minimally adequate but could be improved with explicit safety hints.

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 a single sentence with no filler words. It is front-loaded with the verb and resource, making it efficient and immediately informative.

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?

Given the tool has 12 parameters (2 required) and no output schema, the one-sentence description is insufficient. It does not explain the visualization process, resolution presets, or common usage patterns. More context is needed for an agent to use it effectively among many similar tools.

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

Parameters3/5

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

Input schema has 100% description coverage across all 12 parameters, so baseline is 3. The description adds no additional meaning beyond the schema; it only repeats the overall purpose. No parameter specifics are explained in the description.

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 'Render a field visualization and return a PNG screenshot' clearly states the verb (render), resource (field visualization), and output (PNG screenshot). However, it does not differentiate this tool from siblings like 'cinematic_render' or 'batch_render', which also render visualizations.

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 provides no guidance on when to use this tool versus alternatives. It lacks any context about criteria such as file readiness, prerequisites, or comparative advantages over similar tools like 'preview_3d' or 'volume_render'.

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