Skip to main content
Glama

Thermal Transient Submit

thermal_transient_submit
Destructive

Submits asynchronous transient thermal FEM simulations via Elmer for analytic slabs, FreeCAD solids, or prepared cases, returning a job ID to poll for temperatures and solver results.

Instructions

Transient thermal FEM via Elmer, asynchronous. Requires ElmerSolver (apt elmerfem-csc / conda); when absent this returns {ok:false, reason, install} rather than raising. Three modes:

  • Build the analytic-slab case (no solver case prep needed): pass the plane-wall transient — half_thickness_mm, h_conv (W/m²K), duration_s, and either k+rho+cp (SI) or a material name, with optional t_initial_c / t_ambient_c and mesh/step counts n_elements / n_steps. The handler writes the 1-D conduction case (symmetry at the centre, convection at the surface), runs ElmerSolver, and returns the centre/surface temperatures — the same plane-wall BVP thermal_transient_1d solves analytically, so the two are directly comparable (the kickoff's relative gate).

  • Solve a real FreeCAD solid — the geometry bridge: pass a body handle plus convection_faces (1-based indices into the solid's faces; those faces get the h_conv/t_ambient_c convective BC, every other face is adiabatic), the physics (h_conv, duration_s, k+rho+cp or material), and an optional char_length_mm Gmsh element size and element_order ('1st'|'2nd'). The solid is Gmsh-meshed and solved as a true 3-D body (ElmerGrid + ElmerSolver); the result's {t_max_c, t_min_c} are the interior/convective-surface temperatures (for a slab-like body, directly gateable against thermal_transient_1d). Prefer element_order='2nd' for a sharp transient — quadratic tets resolve the wall gradient accurately even on a coarse mesh.

  • Run a prepared case_dir containing its own .sif + mesh.

Returns the degradation dict, or {job_id, status, cache_hit}; poll job_result for {ok, returncode, solver, case_dir, stdout_tail} plus, for the slab case, {t_center_c, t_surface_c, n_steps_written}, for a body {t_max_c, t_min_c, nodes, tets} (or {scalars_final} for a prepared case).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "thermal_transient_submit"
  }
}

Input Schema

NameRequiredDescriptionDefault
kNo
cpNo
rhoNo
sifNocase.sif
bodyNo
h_convNo
n_stepsNo
case_dirNo
materialNo
workspaceNoRun this call in this named workspace
duration_sNo
n_elementsNo
t_ambient_cNo
t_initial_cNo
element_orderNo
char_length_mmNo
convection_facesNo
half_thickness_mmNo

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

A4.9/5.0
Behavior5/5

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

The description goes well beyond the annotations: it discloses the ElmerSolver dependency, the degradation-dict behavior when the solver is absent, asynchronous submission, the {job_id, status, cache_hit} return, and the need to poll job_result for detailed results. It also states that the handler writes a case and runs ElmerSolver, consistent with destructiveHint=true. This is strong behavioral disclosure for a complex external-solver workflow.

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 long, but the tool has 18 parameters and three distinct modes, so the length is justified. It is front-loaded with the core purpose and async behavior, then organized into clear mode bullets with no obvious filler. Each section provides actionable information for selecting a mode and invoking it correctly.

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

Completeness5/5

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

Although there is no output schema, the description explains the return shapes: the degradation dict, {job_id, status, cache_hit}, and the detailed job_result payloads for slab, body, and prepared cases. Combined with solver-dependency and async-polling guidance, it is complete enough for an agent to invoke and follow up correctly.

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 only 6%, so the description carries most of the burden, and it does so for nearly all meaningful parameters: units for h_conv, half_thickness_mm, duration_s, the k/rho/cp vs material alternative, 1-based convection_faces, and element_order values. The main omission is the sif parameter, which is not explained in the description, though its role is partially implied by case_dir.

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 states a specific verb and resource: transient thermal FEM via Elmer, asynchronously. It clearly distinguishes the three modes, including the analytic-slab path vs the FreeCAD solid geometry bridge vs a prepared case_dir. It also explicitly names thermal_transient_1d as the analytic counterpart, helping an agent distinguish sibling tools.

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

Usage Guidelines5/5

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

The description gives explicit conditions for each mode: use the analytic-slab path with half_thickness_mm/h_conv/duration_s, use the body path with a body handle plus convection_faces, and use case_dir for a prepared case. It also provides a choice rule for element_order, recommending '2nd' for sharp transients. This is close to a complete when/when-not guide.

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