Skip to main content
Glama

Thermal Radiation Submit

thermal_radiation_submit
Destructive

Submits asynchronous Elmer diffuse-gray radiation FEM jobs for a two-plate enclosure or a prepared case, returning net radiative flux and oracle-checked results.

Instructions

Diffuse-gray radiation FEM via Elmer, asynchronous — the radiation sibling of thermal_transient_submit. Requires ElmerSolver + the ViewFactors binary (apt elmerfem-csc / conda); when absent this returns {ok:false, reason, install} rather than raising. Two modes:

  • Build the two-plate enclosure case (no case prep): pass t1_c, t2_c (°C) and the two surface emissivities emissivity_1/emissivity_2 (default 0.8). The handler writes a 2-D pair of parallel plates radiating across an unmeshed vacuum gap, runs ViewFactors then ElmerSolver, and extracts the net radiative exchange — directly gated against the exact two infinite parallel plates oracle q = σ(T₁⁴−T₂⁴)/(1/ε₁+1/ε₂−1) (oracle_ratio ≈ 1). Mesh/geometry knobs: width_m, gap_m, plate_thickness_m, n_x, k_plate.

  • Run a prepared case_dir containing its .sif + mesh (ViewFactors is run first when no factor file is present).

Returns the degradation dict, or {job_id, status, cache_hit}; poll job_result for {ok, returncode, solver, case_dir, stdout_tail} plus, for the plate case, {flux_w_m2, q_net_w, two_plate_flux_w_m2, oracle_ratio, t1_c, t2_c, emissivity_1, emissivity_2} (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_radiation_submit"
  }
}

Input Schema

NameRequiredDescriptionDefault
n_xNo
sifNocase.sif
t1_cNo
t2_cNo
gap_mNo
k_plateNo
width_mNo
case_dirNo
workspaceNoRun this call in this named workspace
emissivity_1No
emissivity_2No
plate_thickness_mNo

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.6/5.0
Behavior5/5

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

Adds substantial context beyond the destructiveHint/readOnlyHint annotations: it names the external runtime dependency (ElmerSolver + ViewFactors, apt/conda packages), discloses that a missing dependency yields {ok:false, reason, install} instead of raising, and explains the async contract (returns job_id/status/cache_hit, poll job_result). The ViewFactors auto-run when no factor file exists is a behavioral detail no structured field carries.

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?

Front-loaded with the one-line identity and dependency caveat, then cleanly sectioned by mode; the oracle formula earns its place because it tells the agent how results are validated. Slightly dense — the parenthetical return-field inventory is heavy — but no sentence is filler.

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?

For an async, dependency-sensitive solver with no output schema, the description covers inputs, mode routing, failure behavior, and the full expected return payload (flux_w_m2, q_net_w, oracle_ratio, scalars_final for prepared cases). An agent has everything needed to invoke it and to interpret the job_result polling step.

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?

With only 8% schema description coverage across 12 parameters, the description has to carry the load, and it does: t1_c/t2_c as °C plate temperatures, emissivity_1/emissivity_2 with the 0.8 default, the geometry knobs width_m/gap_m/plate_thickness_m/n_x/k_plate, and case_dir's expected contents. Gaps remain — units for the mesh/geometry knobs and the role of sif and workspace are not explained here.

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?

States a specific verb+resource (diffuse-gray radiation FEM via Elmer), marks it asynchronous, and explicitly positions it as the radiation sibling of thermal_transient_submit. The two operating modes are enumerated up front, so an agent can distinguish it from thermal_transient_submit and the other thermal tools without opening the schema.

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?

Gives a clear selection rule between the two modes: omit case prep and pass t1_c/t2_c plus emissivities to build the canonical two-plate enclosure, or supply a prepared case_dir containing .sif and mesh. It does not state when this tool should be avoided relative to non-radiation thermal solvers (e.g. thermal_transient_submit, cht_channel_submit), so the exclusion side is only implied.

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