Skip to main content
Glama

compare

Compare two simulation results side-by-side or as a difference map to validate solver accuracy and design changes.

Instructions

Compare two simulation results side-by-side or as a difference map.

Renders both datasets with identical camera, colormap, and scalar range for direct visual comparison. Essential for design comparison, mesh convergence studies, and solver validation.

Modes:

  • side_by_side: Two panels with shared colorbar and consistent framing

  • diff: Absolute field difference map (|A - B|) rendered on dataset A's mesh

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
file_aYesPath to first simulation file
file_bYesPath to second simulation file
field_nameNoField to compare (None for auto-detect)
modeNoComparison mode — "side_by_side" or "diff"side_by_side
colormapNoColor map preset for both panelsCool to Warm
qualityNoRendering quality (draft/standard/cinematic)standard
purposeNoResolution preset — "analyze" (480p), "preview" (720p), "publish" (1080p)analyze
widthNoOverride total width in pixels (must set both width and height, or neither)
heightNoOverride height in pixels (must set both width and height, or neither)
scalar_rangeNoShared [min, max] for consistent coloring (None for auto)
timestepNoSpecific timestep, "latest", or None for first
label_aNoLabel for first panel (displayed top-left)A
label_bNoLabel for second panel (displayed top-left)B
output_filenameNoOutput PNG filenamecompare.png
Behavior4/5

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

With no annotations, the description carries full burden. It explains that identical camera, colormap, and scalar range are used, and details the diff mode. It does not discuss performance limits or error cases, but covers key behavioral traits.

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 concise and well-structured: a one-sentence opening, then bullet points for modes. Every sentence adds value with no wasted words.

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

Completeness4/5

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

Given 14 parameters with full schema coverage and no output schema, the description explains behavior and modes sufficiently. It covers enough for an agent to select and invoke the tool, though it could mention the output image destination.

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?

Schema description coverage is 100%, so the baseline is 3. The description adds context about shared colormap/scalar range and label placement, but the schema already adequately describes each parameter.

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 verb "compare" and resource "simulation results", with modes side_by_side and diff. It distinguishes from sibling tools by specifying use cases like design comparison and solver validation, making the purpose unambiguous.

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

Usage Guidelines4/5

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

The description provides explicit use cases (design comparison, mesh convergence, solver validation) and explains both modes. However, it does not explicitly state when to avoid this tool or name specific alternatives among the many siblings, slightly reducing guidance.

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