Skip to main content
Glama

Acoustic Screen

acoustic_screen
Read-only

Calculate closed-form acoustic screening values—cavity modes, Helmholtz resonance, mass-law transmission loss, and duct cutoff—to flag when a FEM solve is needed.

Instructions

Closed-form acoustics screen (NO solver). kind: 'cavity_modes' (lx/ly/lz_mm -> the lowest n_modes rigid-cavity eigenfrequencies f=(c/2)·√(Σ(n/L)²) with [nx,ny,nz] indices — exact, and the future oracle for the planned Elmer HelmholtzSolve FEM) | 'helmholtz' (neck_area_mm2 + neck_length_mm + cavity_volume_mm3 -> resonance with flanged end correction — ±10 %) | 'mass_law' (frequency_hz + surface_density_kg_m2 -> limp-wall TL = 20·log₁₀(f·m″)−47 dB — ±3 dB) | 'duct_cutoff' (duct_width_mm or duct_diameter_mm -> first cross-mode; plane waves only below — exact). Sound speed from air at t_ambient_c unless c_m_s given. Fidelity is labeled per kind; escalate to the Elmer acoustic_fem_submit solve (Tier B1) when the margin is within ~2× the band.

Returns {kind, c_m_s, fidelity, band_pct, band_db, valid_range_ok, warnings, escalate_to} plus per kind: {modes:[{f_hz,n}], f_fundamental_hz} | {f_resonance_hz, neck_radius_mm, l_eff_mm} | {tl_db, fm_product} | {f_cutoff_hz, geometry}.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "kind": "<kind>"
    },
    "name": "acoustic_screen"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindYes
c_m_sNo
lx_mmNo
ly_mmNo
lz_mmNo
n_modesNo
workspaceNoRun this call in this named workspace
t_ambient_cNo
frequency_hzNo
duct_width_mmNo
neck_area_mm2No
neck_length_mmNo
duct_diameter_mmNo
cavity_volume_mm3No
surface_density_kg_m2No

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

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

Annotations only declare readOnlyHint and openWorldHint; the description adds a great deal beyond them: per-kind fidelity bands (±10% for helmholtz, ±3 dB for mass_law, 'exact' for cavity/duct), the physical assumptions (flanged end correction, limp wall, plane waves only), the sound-speed default from t_ambient_c, and the presence of warnings/escalate_to in the response.

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?

Dense but well front-loaded: the tool's nature and the NO-solver constraint come first, then per-kind semantics, then return shape. The pipe-and-arrow notation is compact; a small amount of formula detail could be trimmed, but nothing is filler.

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?

For a 15-parameter, no-output-schema tool this is complete: it explains each kind's inputs and outputs, the fidelity/accuracy of each result, the escalation path, and the default sound-speed behavior. An agent can call it and interpret the response without further lookup.

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 description coverage is only 7%, so the description has to carry the parameter burden and mostly does: it maps each kind to its required inputs (lx/ly/lz_mm for cavity_modes, neck_area_mm2 + neck_length_mm + cavity_volume_mm3 for helmholtz, frequency_hz + surface_density_kg_m2 for mass_law, duct_width_mm or duct_diameter_mm for duct_cutoff) and explains c_m_s and t_ambient_c. Only n_modes and workspace are left implicit.

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 ('Closed-form acoustics screen (NO solver)') and immediately enumerates four named kinds with the governing formulas. It is unambiguously distinguishable from the solver siblings like acoustic_fem_submit or acoustic_radiation_submit.

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?

Gives an explicit escalation rule ('escalate to the Elmer acoustic_fem_submit solve (Tier B1) when the margin is within ~2× the band'), which tells the agent when this screen is no longer sufficient. It does not, however, disambiguate against adjacent analytic siblings such as waveguide_cutoff or dipole_resonance, leaving some overlap 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