Skip to main content
Glama

EM Conduction Submit

em_conduction_submit

Submits an asynchronous Elmer DC conduction simulation for a rectangular conductor, returning job status or current, Joule heating, and resistance results.

Instructions

DC current conduction via Elmer's StatCurrentSolver (P3 M6 frontier), asynchronous. Requires ElmerSolver; when absent this returns {ok:false, reason, install} rather than raising. Builds a rectangular strip with voltage_v across its ends and reads the electrode current, total Joule heating and Elmer's effective resistance — all machine-exact against R = L/(σ·A) (resistance_ratio = 1.000000 live).

Returns the degradation dict or {job_id, status, cache_hit}; poll job_result for {ok, current_a, joule_w, effective_resistance_ohm, resistance_exact_ohm, current_exact_a, resistance_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_conduction_submit"
  }
}

Input Schema

NameRequiredDescriptionDefault
nxNo
nyNo
width_mNo
length_mNo
conductorNocopper
voltage_vNo
workspaceNoRun this call in this named workspace
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 already declare non-read-only, non-destructive, closed-world, but the description adds behavior the annotations cannot: the call is asynchronous, it degrades gracefully to {ok:false, reason, install} instead of raising when ElmerSolver is missing, and it may return a cached result via cache_hit. It also enumerates the return contract (job_id/status or the degradation dict) so the agent knows exactly what to inspect.

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?

Purpose, prerequisite, and return contract are front-loaded and each sentence carries information (solver, fallback, outputs, polling). Some phrases are opaque filler for an agent ('P3 M6 frontier', 'a degradation dict') and could be replaced with plainer wording.

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 async FEM submit with no output schema, the description covers what matters most: the missing-solver failure mode, the async/polling contract, and the exact result keys. The remaining gap is that several mesh and material-override parameters are undocumented, so an agent cannot confidently tune resolution or know which conductivity source wins.

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 must compensate, and it does partly: voltage_v is explained as applied across the strip ends and the R = L/(σ·A) relation ties length, conductivity, and cross-section to the output. But nx/ny (mesh resolution), the conductor-vs-conductivity_s_m override relationship, and the implicit cross-section (no thickness parameter) are left unexplained.

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 names a specific verb (submit DC current conduction) and the exact solver backend (Elmer's StatCurrentSolver), and states precisely what physics is computed: current, Joule heating, and effective resistance from a rectangular strip with voltage_v across its ends. An agent can distinguish this from analytic siblings like em_dc_resistance or field solvers like em_field 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?

It gives an explicit prerequisite (requires ElmerSolver) and the exact next step after submission (poll job_result), which is the key routing decision for an async tool. It does not, however, state when to use this FEM submission instead of the analytic siblings such as em_dc_resistance or em_induction_submit, leaving that inference to the agent.

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