Skip to main content
Glama

EM Induction Submit

em_induction_submit

Submits an asynchronous Elmer simulation to compute AC skin effect and induction heating in a conductor slab, returning a job ID for polling results.

Instructions

AC skin effect / induction via Elmer's harmonic 2-D magnetodynamics (P3 M6 frontier), asynchronous. Requires ElmerSolver; when absent this returns {ok:false, reason, install} rather than raising. Builds a conductor slab depths skin depths deep driven by the surface vector potential at frequency_hz, solves the complex field, and fits the e-folding length of BOTH the magnitude and the phase of A(x) — each must equal the exact δ = √(2/(ω·μ₀·μ_r·σ)) (live: decay_ratio 0.999, phase_ratio 1.000). The Joule deposition profile |J|² ∝ e^(−2x/δ) is the induction-heating answer.

Returns the degradation dict or {job_id, status, cache_hit}; poll job_result for {ok, skin_depth_exact_m, decay_length_m, phase_length_m, decay_ratio, phase_ratio, 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_submit"
  }
}

Input Schema

NameRequiredDescriptionDefault
nxNo
nyNo
mu_rNo
depthsNo
conductorNocopper
workspaceNoRun this call in this named workspace
frequency_hzNo
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

A3.7/5.0
Behavior4/5

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

Annotations only mark it as a non-read-only, non-destructive, closed-world mutation. The description adds real value beyond that: async job semantics, the solver dependency, graceful degradation instead of an exception, an embedded self-validation criterion (decay_ratio 0.999, phase_ratio 1.000), and the shape of the returned dicts. It does not discuss runtime cost or failure modes of the fit itself.

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 core identity and job model, then geometry, then return contract. Mostly dense and purposeful, though phrases like '(P3 M6 frontier)' and the inline 'live: decay_ratio 0.999' figures are decorative rather than actionable for an agent.

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?

With no output schema and 8 parameters, the description does the heavy lifting: it names the submit return ({job_id, status, cache_hit}), the degradation dict, and the fields available from job_result. The remaining gap is mesh parameters (`nx`, `ny`) and `conductor`, which an agent must guess at.

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% (just `workspace`), so the description has to carry most parameters. It does explain `depths`, `frequency_hz`, `mu_r` and `conductivity_s_m` implicitly through the δ = √(2/(ω·μ₀·μ_r·σ)) formula and the slab geometry, but `nx`/`ny` (mesh resolution) and `conductor` selection semantics are left entirely unexplained.

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+resource: submits an asynchronous AC skin-effect/induction solve using Elmer's harmonic 2-D magnetodynamics, including the physical construction (conductor slab `depths` skin depths deep, driven at `frequency_hz`). It is clearly distinguishable in substance from a simple `em_skin_depth` calculator, but it never names the sibling tools (em_skin_depth, em_induction_heating_submit, em_conduction_submit) to route the agent explicitly.

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?

Gives useful operating context: it is asynchronous, requires ElmerSolver, degrades to {ok:false, reason, install} instead of raising, and you must poll job_result. However there is no explicit guidance on when to choose this over `em_skin_depth` or `em_induction_heating_submit`, and no prerequisites or exclusions beyond the solver requirement.

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