Skip to main content
Glama

EM Induction Heating Submit

em_induction_heating_submit
Destructive

Submits an asynchronous Elmer coupled induction-heating simulation that calculates eddy-current Joule losses and transient adiabatic temperature rise, returning a job ID for result polling.

Instructions

Coupled induction heating via Elmer (SIMULATION_NEXT B5), asynchronous — completes em_induction_submit into a THERMAL answer: the harmonic MagnetoDynamics solve runs once, MagnetoDynamicsCalcFields turns it into the time-averaged Joule loss field, and a transient adiabatic HeatSolver integrates it for heat_duration_s. Requires ElmerSolver; when absent this returns {ok:false, reason, install} rather than raising.

Two gates: joule_power_ratio — the solved eddy-current power vs the exact deep-slab dissipation P″ = R_s·|H₀|²/2 = ω²σA₀²δ/4 (from the shipped em_skin_depth chain; live 1.0003) — and energy_balance_ratio — the mean temperature rise vs P·t/(m·cₚ) (live 1.005). Conductor σ from a name or explicit conductivity_s_m; thermal ρ/cₚ/k explicit. Also accepts a prepared case_dir.

Returns the degradation dict or {job_id, status, cache_hit}; poll job_result for {ok, eddy_power_w_m, p_total_exact_w_m, joule_power_ratio (≈1), t_mean_final_k, dt_mean_exact_k, energy_balance_ratio (≈1), skin_depth_m, case_dir}.

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": "em_induction_heating_submit"
  }
}

Input Schema

NameRequiredDescriptionDefault
nxNo
nyNo
sifNocase.sif
mu_rNo
depthsNo
n_stepsNo
case_dirNo
cp_j_kgkNo
a_surfaceNo
conductorNocopper
k_thermalNo
workspaceNoRun this call in this named workspace
frequency_hzNo
density_kg_m3No
heat_duration_sNo
conductivity_s_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.3/5.0
Behavior5/5

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

Annotations only say destructive/not-read-only; the description adds far more: asynchronous job semantics, cache_hit, degradation dict on missing ElmerSolver instead of raising, the case_dir bypass, and the two verification gates with expected ~1 ratio values. That is substantive behavioral context beyond structured fields, and nothing contradicts the destructiveHint=true annotation.

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 coupled-solve summary, then gates, then return shape, so the agent can stop reading early. Slightly bloated by the inline equations (P″ = R_s·|H₀|²/2 …) which are precise but not needed for tool selection.

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?

For an asynchronous, destructive, no-output-schema tool it covers the essentials: what returns immediately ({job_id, status, cache_hit}), how to retrieve results (job_result fields), and the failure path. The remaining gap is that over half the input parameters have no documented meaning anywhere.

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 6% across 16 params, so the description must carry the load. It does explain the physics-bearing inputs (heat_duration_s, conductivity_s_m vs a named conductor, explicit ρ/cₚ/k, case_dir), but the mesh/numerics params (nx, ny, n_steps, sif, mu_r, depths, a_surface) and workspace semantics are left undocumented in both schema and description.

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 (submit a coupled induction-heating solve) and resource, and explicitly positions it against siblings: it "completes em_induction_submit into a THERMAL answer" while em_induction_submit stays magnetic-only. The pipeline (MagnetoDynamics solve → CalcFields Joule loss → transient HeatSolver) makes the deliverable 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?

Clear context: use when you need the eddy-current-to-temperature coupling with a transient heat duration, and it names the sibling it extends (em_induction_submit). It also tells the agent to poll job_result after submit. It stops short of explicit exclusions or naming alternatives like thermal_transient_submit/em_conduction_submit when heating is not the goal.

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