Skip to main content
Glama

render

Visualize a field from your simulation file and output a customizable PNG screenshot. Adjust colormap, camera, resolution, and timestep to capture the exact view you need.

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
Behavior2/5

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

With no annotations, the description must disclose behavioral traits. It mentions returning a PNG screenshot but omits side effects like file saving (via 'output_filename') and does not explain what happens during rendering (e.g., data loading, potential performance impact).

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?

The description is a single sentence without fluff, but the phrase 'return a PNG screenshot' could mislead about the actual behavior (saving to file vs. returning binary data). Still, it is efficient.

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 tool with 12 parameters and no output schema, the description is too minimal. It does not explain resolution presets, camera presets, timestep selection, or multiblock handling, leaving the agent underinformed.

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?

The input schema covers all 12 parameters with descriptions (100% coverage), so the description adds no extra parameter meaning. Baseline of 3 is appropriate.

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 action ('Render'), the target resource ('a field visualization'), and the output format ('PNG screenshot'). This distinguishes it from sibling tools like 'animate' or 'preview_3d'.

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 'render' versus alternatives like 'preview_3d', 'batch_render', or 'cinematic_render'. There are no context cues for tool selection.

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