Skip to main content
Glama

Rigid Sphere Scattering

rigid_sphere_scattering
Read-only

Compute exact rigid-sphere plane-wave scattering far-field form functions via the Mie series to validate BEM acoustic scattering results and backscatter limits.

Instructions

Exact rigid-sphere plane-wave scattering far-field form function via the Mie series (NO solver) — the closed-form twin the Bempp exterior-acoustics BEM scattering solve (acoustic_radiation_submit, problem='scattering') is gated against. For compactness ka and scattering angle theta_deg (from the forward direction; 180° is backscatter), f∞(θ) = (2/ika)·Σₙ(2n+1)[−j'ₙ(ka)/h'ₙ(ka)]· Pₙ(cosθ) — a rigorous spherical-harmonic sum (Neumann ∂p/∂r=0 on the sphere) truncated past convergence (fidelity='exact'). The backscatter |f∞(π)| → 1 in the geometric (ka≫1) limit and rises through the resonance region. A BEM scattered far field must land on |f∞(θ)|.

Returns {ka, theta_deg, a_m, form_function_abs, form_function_re, form_function_im, backscatter_abs, n_terms, 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": {
      "ka": "<ka>"
    },
    "name": "rigid_sphere_scattering"
  }
}

Input Schema

NameRequiredDescriptionDefault
kaYes
a_mNo
theta_degNo
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/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered; the description adds real behavioral substance — no solver, series truncated past convergence, fidelity='exact', and returned diagnostics (valid_range_ok, band_pct, warnings, escalate_to) that signal out-of-range behavior. It does not state cost/scaling with ka or what concretely triggers warnings or escalation, which keeps it below a 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The identifying clause is front-loaded, but the body is a single dense run of Mie-series notation and physics commentary (geometric limit, resonance region) that an agent does not need in order to select or call the tool. It is informative rather than wasteful, yet several clauses could be compressed without losing selectable meaning.

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?

With no output schema, the description usefully enumerates the returned keys (form_function_abs/re/im, backscatter_abs, n_terms, fidelity, warnings, escalate_to) and explains the validity diagnostics, which is exactly the missing structure. Remaining gaps are the unexplained `a_m` parameter and unspecified units/ranges for ka.

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 25% (only `workspace` is documented), so the description must compensate. It does define `ka` (compactness) and `theta_deg` (angle from forward direction, 180° = backscatter), but `a_m` — the sphere radius appearing in the formula and the return set — is never explained, and no units are given for ka or a_m.

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 computation (exact rigid-sphere plane-wave far-field form function via the Mie series, no solver) with a precise verb+resource, and explicitly positions it against the sibling `acoustic_radiation_submit` (problem='scattering') as the analytic reference it is gated against. An agent can distinguish it from `monopole_sphere`, `dipole_resonance`, and the BEM solve without opening any 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?

Usage context is clear: it is the closed-form twin a BEM scattered far field 'must land on', which tells the agent to reach for it as a validation/reference baseline rather than as a solver. It stops short of an explicit when-not clause or naming the alternative path for a full-field solve, so it is strong context but not a full routing 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