Skip to main content
Glama

Acoustic FEM Submit

acoustic_fem_submit
Destructive

Submits asynchronous acoustic FEM simulations for duct and cavity cases via Elmer HelmholtzSolve, returning a job ID for polling or a degradation response if ElmerSolver is missing.

Instructions

Acoustic FEM via Elmer HelmholtzSolve (SIMULATION_NEXT Tier B1), asynchronous — the higher-order twin of acoustic_screen, gated against its exact closed forms. Requires ElmerSolver; when absent this returns {ok:false, reason, install} rather than raising.

kind='duct': a closed duct driven p=1 at x=0, rigid at x=L, at f = kL·c/(2πL) (keep kl off the quarter-wave resonances) — the rigid-end pressure has the exact oracle 1/cos(kL), so p_end_ratio ≈ 1 machine-tight. kind='cavity': a rigid lx_m × ly_m cavity excited by a corner Wave Flux source, swept ±span_pct% around the exact (mode_nx, mode_ny) eigenfrequency in n_steps Scanning steps; the in-phase corner-probe response flips sign through resonance, and the 1/A zero-crossing gives f_solved_hz with mode_ratio ≈ 1 (<0.1%). Also accepts a prepared case_dir.

Returns the degradation dict or {job_id, status, cache_hit}; poll job_result for duct {ok, p_end_re, p_end_exact, p_end_ratio (≈1), p_mean_ratio, frequency_hz, case_dir} | cavity {ok, f_solved_hz, f_exact_hz, mode_ratio (≈1), mode, 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": "acoustic_fem_submit"
  }
}

Input Schema

NameRequiredDescriptionDefault
klNo
nxNo
nyNo
sifNocase.sif
kindNoduct
lx_mNo
ly_mNo
c_m_sNo
mode_nxNo
mode_nyNo
n_stepsNo
case_dirNo
length_mNo
span_pctNo
workspaceNoRun this call in this named workspace
n_elementsNo

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.1/5.0
Behavior4/5

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

Adds real behavior beyond the annotations: requires ElmerSolver and returns {ok:false, reason, install} instead of raising when absent, is asynchronous (returns {job_id, status, cache_hit}), and requires polling `job_result` for the payload — plus a cache_hit signal. It does not explain the destructiveHint=true implication (writing/overwriting case dirs), which is the one behavior an agent should know before running it.

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, solver, and async behavior before the per-kind detail, and every sentence carries technical information. It is dense with oracle notation but not padded — the length is justified by two distinct modes and a non-trivial result contract.

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 a 16-parameter async solver with no output schema, the description gives a usable return contract (duct: p_end_ratio, p_mean_ratio; cavity: f_solved_hz, mode_ratio) and the degradation path. Remaining gaps are mesh/parameter semantics rather than missing decision-relevant behavior.

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 coverage is only 6%, so the description carries the burden and does partially: it explains `kl`, `kind`, `lx_m`/`ly_m`, `mode_nx`/`mode_ny`, `n_steps`, `span_pct`, and `case_dir`. However, `nx`, `ny`, `n_elements`, `sif`, `c_m_s`, and `length_m` (mesh resolution and file/sound-speed inputs) are never explained, leaving several of 16 parameters 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+resource (acoustic FEM via Elmer HelmholtzSolve, asynchronous submit) and explicitly positions itself as the 'higher-order twin of acoustic_screen, gated against its exact closed forms', which distinguishes it from the screening sibling without needing the schema. The two supported `kind` cases are spelled out, so an agent knows exactly what physics this tool covers.

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 for each mode: duct needs `kl` kept off quarter-wave resonances, cavity sweeps ±span_pct around the exact eigenfrequency, and a prepared `case_dir` is also accepted. The implied workflow vs. `acoustic_screen` (screen first, then validate with FEM) is present but not stated as an explicit when/when-not rule.

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