Skip to main content
Glama

Monopole Sphere

monopole_sphere
Read-only

Compute exact radiated power and far-field pressure for a pulsating sphere, providing closed-form validation for BEM exterior-acoustics radiation solves.

Instructions

Exact pulsating (monopole) sphere radiated power + far-field pressure (NO solver) — the closed-form twin the Bempp exterior-acoustics BEM radiation solve (acoustic_radiation_submit) is gated against. A sphere of radius a_m vibrating with uniform surface normal velocity u_amp at freq_hz radiates W = (ρc/2)|U|²(4πa²)(ka)²/(1+(ka)²) and, at range r_m, |p(r)| = ρc|U|·ka/√(1+(ka)²)·(a/r) — both EXACT. The radiation efficiency σ=(ka)²/(1+(ka)²) → 0 (poor sub-wavelength radiator) as ka→0 and → 1 as ka→∞. rho/c default to air at 20 °C. A BEM Neumann (velocity) solve must reproduce W and |p(r)|.

Returns {a_m, freq_hz, k_per_m, ka, u_amp, rho, c, radiation_efficiency, radiated_power_w, surface_pressure_abs, r_m, farfield_pressure_abs, farfield_pressure_x_r, fidelity, band_pct, valid_range_ok, warnings, escalate_to}.

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": {
      "a_m": "<a_m>",
      "freq_hz": "<freq_hz>"
    },
    "name": "monopole_sphere"
  }
}

Input Schema

NameRequiredDescriptionDefault
cNo
a_mYes
r_mNo
rhoNo
u_ampNo
freq_hzYes
workspaceNoRun this call in this named workspace

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 already establish `readOnlyHint: true` and `openWorldHint: false`, but the description adds substantial behavioral context: no solver, exact formulas, uniform surface normal velocity assumption, default air properties, radiation-efficiency limits, and output fields including validity and escalation signals. This is well beyond what the annotations provide.

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?

The definition is front-loaded with the core purpose and remains focused on relevant formulas, assumptions, and return fields. It is dense and includes a long return-field list, but because there is no output schema, that information earns its place.

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 complex analytical acoustics tool with low schema description coverage and no output schema, the description supplies the governing formulas, assumptions, defaults, radiation-efficiency behavior, and return-field inventory. An agent has enough context to invoke it correctly and interpret the key outputs.

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 14% and parameter titles are cryptic, so the description carries most of the burden. It meaningfully defines `a_m`, `freq_hz`, `u_amp`, `r_m`, `rho`, and `c` through the physical model, though it stops short of explicit units/defaults for some optional inputs and relies on the schema for `workspace`.

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 states a specific verb/resource: exact closed-form radiated power and far-field pressure for a pulsating monopole sphere, explicitly with "NO solver." It also distinguishes itself from the BEM sibling `acoustic_radiation_submit` by positioning itself as the closed-form twin that the BEM solve is gated against.

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 clear context that this is an analytical reference/benchmark for the BEM radiation solve, which helps an agent choose it over `acoustic_radiation_submit` when a closed-form check is desired. However, it does not explicitly state exclusions, such as non-spherical geometry or when an actual BEM solve is required.

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