Skip to main content
Glama

Render FEM Results

render_fem_results
Read-only

Renders completed FEM result surfaces with field-based viridis coloring, deformed-shape overlay, and min/max colorbar to visualize stress, displacement, or temperature solves as a PNG.

Instructions

Render a completed FEM result's surface, colored by a per-vertex field.

Pulls the result surface (boundary triangulation + per-node field values + displacement vectors) from the worker, then colors it with a viridis colormap (barycentrically interpolated), overlays the deformed shape, and draws a colorbar with the field min/max — the "agent eyes" for a stress / displacement / thermal solve.

field: 'vonmises' (default) | 'displacement' | 'temperature'. view: a preset ('iso'|'top'|'front'|…) or a custom '(azimuth,elevation)' camera passed as e.g. "45,35". deformation_scale: 'auto' scales the peak displacement to ~8% of the model diagonal; a number is used verbatim; '0' disables the deformed overlay.

Returns {png_base64, width, height, field, units, min, max, view, node_count, triangle_count}.

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": {
      "analysis": "<analysis>"
    },
    "name": "render_fem_results"
  }
}

Input Schema

NameRequiredDescriptionDefault
viewNoiso
edgesNo
fieldNovonmises
widthNo
heightNo
analysisYes
workspaceNoRun this call in this named workspace
deformation_scaleNoauto

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.5.7
    • addedInput schema / properties / workspace
      Added value: +{
      +  "default": "",
      +  "description": "Run this call in this named workspace",
      +  "title": "Workspace",
      +  "type": "string"
      +}
  2. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, but the description adds substantive behavior: it pulls the boundary triangulation, node fields, and displacements from the worker, applies a viridis colormap, overlays deformed geometry, and draws a colorbar. It also specifies the deformation_scale semantics and return keys, though it does not mention failure conditions or prerequisites such as whether the analysis must already be solved.

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 front-loaded with the core operation, then gives parameter semantics and the return shape. It is dense and mostly waste-free, with only minor flavor in the 'agent eyes' phrasing.

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?

It supplies a return-value summary despite there being no output schema, and it explains rendering behavior well. But for an 8-parameter tool with only 13% schema description coverage and no output schema, the unexplained required 'analysis' parameter and undocumented edges/width/height leave real gaps.

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 only 13%, so the description must carry most parameter meaning. It nicely documents field, view, and deformation_scale with accepted values and defaults, but the required 'analysis' parameter plus edges, width, and height are left undocumented, so the coverage gap is only partially compensated.

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?

States a specific verb and resource: renders a completed FEM result's surface colored by a per-vertex field. The field and view options make the purpose concrete, but it does not explicitly distinguish itself from nearby siblings such as fem_results, fem_result_probe, render_view, or render_views.

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?

Implies usage after a completed solve by saying 'completed FEM result' and documenting the field/view options. However, it never states when to use this instead of fem_results, fem_result_probe, or render_view/render_views, leaving alternative selection to inference.

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