Skip to main content
Glama

Acoustic Radiation Submit

acoustic_radiation_submit

Submits asynchronous exterior-acoustics boundary-element solves for radiation, scattering, or FreeCAD mesh models, returning a job ID to poll for results.

Instructions

Exterior-acoustics boundary-element solve on Bempp, asynchronous (OFF the MCP channel) — the real-field twin of the analytic monopole_sphere / rigid_sphere_scattering oracles. Bempp is MIT but needs meshio>=4 (clashing with solidspy's meshio==3 in the shared venv), so it is run ONLY out-of-process via ankusdrive/bempp_runner.py under a dedicated .venv-bempp; degrades to {ok:false, reason, install} when no bempp venv resolves.

problem='radiation' (default): a pulsating (monopole) sphere of radius a_m, uniform surface velocity u_amp at freq_hz, into air (rho,c), mesh size h (fraction of a). The result's radiated_power_w / farfield_pressure_x_r vs the monopole_sphere oracle (ratio≈1) IS the gate. problem='scattering': a rigid sphere insonified by a unit plane wave; sweep ka_list, report the far-field form function at theta_deg angles (h_per_wl elements/wavelength) — gated against the rigid_sphere_scattering Mie oracle. problem='mesh_solve': a radiation solve on a REAL FreeCAD model (handle), tessellated to a surface mesh here and fed to the BEM engine (scale_to_m mm→m, linear_deflection mesh tolerance).

Returns the degradation dict, or {job_id, status, cache_hit}; poll job_result for {ok, ka, radiated_power_w, farfield_pressure_x_r, surface_pressure_abs_mean, n_elements, wall_s} (radiation/mesh_solve) or {results:[{ka, form_function_abs{}, backscatter_abs, n_elements}]} (scattering).

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

Input Schema

NameRequiredDescriptionDefault
cNo
hNo
a_mNo
r_mNo
rhoNo
modelNo
u_ampNo
freq_hzNo
ka_listNo
problemNoradiation
timeoutNo
h_per_wlNo
theta_degNo
workspaceNoRun this call in this named workspace
scale_to_mNo
linear_deflectionNo

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/5.0
Behavior5/5

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

Rich disclosure beyond annotations: asynchronous execution off the MCP channel, the out-of-process venv-bempp requirement and why (meshio version clash), the concrete degradation dict {ok:false, reason, install} when no venv resolves, and the need to poll job_result. Annotations only give the generic readOnly/destructive/openWorld hints, so the description carries real behavioral weight.

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-loads purpose, then modes, then return shapes; every paragraph is information-dense with no filler. It is long, and the meshio/solidspy version detail is arguably more than an agent needs to select the tool, but it earns most of its space.

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, no-output-schema, async tool, the description covers mode semantics, failure behavior, and both return shapes (radiation/mesh_solve vs scattering). Only a few parameter gaps (r_m, timeout, workspace) and lack of explicit sibling routing keep it from 5.

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

Parameters4/5

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

Schema coverage is only 6%, so the description must compensate and largely does: it explains problem modes, a_m, u_amp, freq_hz, rho, c, h (fraction of a), ka_list, theta_deg, h_per_wl, model, scale_to_m, linear_deflection. r_m, timeout, and workspace are left undocumented, keeping it below 5.

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 and resource: 'Exterior-acoustics boundary-element solve on Bempp, asynchronous'. It distinguishes itself from the analytic oracles (monopole_sphere / rigid_sphere_scattering) it is the 'real-field twin' of, and from in-process tools via the out-of-process venv note. It does not explicitly contrast with sibling acoustic_fem_submit, so it falls short of a 5.

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?

The three problem modes (radiation/scattering/mesh_solve) are described with their configurations, which implies usage, but there is no explicit 'use this instead of X when Y' guidance. Nothing tells the agent when to prefer this over acoustic_fem_submit or the analytic oracles beyond the 'twin' framing.

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