Skip to main content
Glama

EM Fullwave Submit

em_fullwave_submit

Submits an asynchronous openEMS FDTD simulation for waveguide cutoff sweeps or dipole S11 resonance analysis, returning a job ID to poll for solved fields and metrics.

Instructions

Full-wave FDTD EM solve on openEMS, asynchronous (OFF the MCP channel) — the real-field twin of the analytic waveguide_cutoff / dipole_resonance oracles. openEMS is GPL-3.0 and is run ONLY out-of-process via ankusdrive/em_fullwave_gpl_runner.py; degrades to {ok:false, reason, install} when no openEMS venv resolves.

problem='waveguide_sweep' (default): hollow rectangular guide, broad wall a_mm/narrow wall b_mm (default a/2), length length_mm (default 120), TE10 port at each end. Sweep f_start_ghz..f_stop_ghz (default 4..10 GHz — straddling the WR-90 cutoff 6.56 GHz) in n_freq points, nrts max timesteps, cells_per_wl mesh density, eps_r fill, end_criteria energy stop (1e-6). THE GATE IS alpha_ratio≈1: voltage probes along the guide read the SOLVED field's decay rate below cutoff at decay_f_ratio·f_c (default 0.7) against the exact α = sqrt((π/a)² − k²); it degrades under a coarse mesh or a truncated nrts. alpha_ratio is null with a decay_note when the guide is too short for the probe window. fc_ratio (half-power crossing vs c/2a) is only a PORT-SETUP CHECK: openEMS's analytic port β zeroes every sub-cutoff sample, so it reads the frequency grid, not the field. A degenerate mesh/length (port blocks overlapping) returns {ok:false, error}. problem='dipole_s11': centre-fed thin dipole (length_mm, gap_mm, radius_mm, each resolved by its own mesh lines), sweep S11, report first resonance. Mesh is mesh_res_mm, else λ(mesh_f_ghz, default f_stop) / cells_per_wl (default 30) — pin it to vary the sweep window alone.

Returns the degradation dict, or {job_id, status, cache_hit}; poll job_result for {ok, fc_analytic_ghz, freq_ghz[], s21_db[], transmission_norm[], alpha_fdtd, alpha_exact, alpha_ratio, decay_freq_ghz, decay_probe_z_mm[], decay_fit_rms_np, fc_crossing_ghz, fc_ratio, evanescent_mean, propagating_mean, mesh_res_mm, n_cells, wall_s} (waveguide) or {freq_ghz[], s11_db[], resonance_ghz, resonance_s11_db, mesh_res_mm, n_cells} (dipole).

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_fullwave_submit"
  }
}

Input Schema

NameRequiredDescriptionDefault
a_mmNo
b_mmNo
nrtsNo
eps_rNo
gap_mmNo
n_freqNo
problemNowaveguide_sweep
timeoutNo
length_mmNo
radius_mmNo
workspaceNoRun this call in this named workspace
f_stop_ghzNo
mesh_f_ghzNo
f_start_ghzNo
mesh_res_mmNo
cells_per_wlNo
end_criteriaNo
decay_f_ratioNo

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. Changed4 schema fields changedv0.5.5
    • addedInput schema / properties / decay_f_ratio
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "number"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "title": "Decay F Ratio"
      +}
    • addedInput schema / properties / end_criteria
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "number"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "title": "End Criteria"
      +}
    • addedInput schema / properties / mesh_f_ghz
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "number"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "title": "Mesh F Ghz"
      +}
    • addedInput schema / properties / mesh_res_mm
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "number"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "title": "Mesh Res Mm"
      +}
  3. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations only cover the safety profile (readOnly=false, destructive=false, openWorld=false). The description adds substantial beyond that: async off-channel execution, GPL-3.0 out-of-process runner, degradation to {ok:false, reason, install} with no venv, degenerate-mesh failure, the {job_id, status, cache_hit} submission contract, and job_result polling. This is rich behavioral context the annotations cannot convey.

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 purpose and scope, and nearly every sentence adds operational value (gates, degradation, mesh rules, return fields). The tradeoff is a very dense, backtick-heavy wall of text that is harder to parse than it needs to be, but little is genuinely wasted.

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?

Despite no output schema and near-zero schema coverage, the description enumerates the full return payloads for both problem modes and the async polling path, covers all 18 params, and discloses failure/degradation modes. An agent has everything needed to submit, poll, and interpret results.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With only 6% schema description coverage, the description carries the burden and does so thoroughly, giving meaning and defaults for a_mm/b_mm/length_mm, f_start/f_stop_ghz, n_freq, nrts, cells_per_wl, eps_r, end_criteria, decay_f_ratio, problem, and the dipole mesh/gap/radius params — far beyond the bare schema titles. It explains the mesh-selection rule (mesh_res_mm else λ(mesh_f_ghz)/cells_per_wl) that would otherwise be opaque.

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 and resource: 'Full-wave FDTD EM solve on openEMS, asynchronous', and explicitly positions it as 'the real-field twin of the analytic waveguide_cutoff / dipole_resonance oracles', distinguishing it from those siblings. An agent can tell exactly what this does and how it differs from the analytic oracles without opening a 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?

The 'real-field twin of the analytic ... oracles' framing signals when to prefer this over the analytic siblings, and it explains the two problem modes plus the alpha_ratio gate for judging result validity. It stops short of an explicit 'use waveguide_cutoff instead when you only need a quick estimate' rule, leaving some routing to inference.

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