← All engines

RUST ENGINE / hear_the_shape

Hear the shape of a polygonal drum

Compute vibration modes of a supplied polygon, inspect its nodal patterns and compare the spectra of two shapes under an ideal membrane model.

Open the hear_the_shape demonstration ↗Try the live calculation ↗Connect an AI assistant →

What does a real call return?

For a 0.5 m fixed-edge square, the first extrapolated eigenvalue is 78.957, against the closed-form value 8π² = 78.957. With a wave speed of 100 m/s, that mode is 141.42 Hz.

Recorded on 2 November 2026 through the public MCP endpoint, service release 0.17.1. Inputs and full responses, response SHA-256 7f697f205403…. Verdict values are the literal values the tool returns. Run the same inputs yourself to compare; elapsed times vary, and a new release may change the figures.

Checked against

Recorded on release 0.16.1. These checks cover the listed cases, not every input. Evidence cards.

How it works

Rust assembles piecewise-linear finite elements on three nested meshes to solve the fixed-edge or free-edge Laplacian problem. Finite-element eigenvalues and Richardson-extrapolated estimates are reported separately. The finest mesh is bounded to 50,000 triangles; a smaller mesh can carry normalized mode values for visualization.

Inputs and units

Supply a simple polygon with 3–64 vertices in metres, optionally repeating its first point at the end. Coordinates are bounded to ±10,000 m. Request 1–12 modes with fixed or free boundary conditions. An optional second polygon enables comparison; an explicit wave speed in m/s enables frequencies and musical notes.

What the result contains

Eigenvalue upper bounds under the stated numerical assumptions, extrapolated estimates and estimated errors, resolution warnings, nodal-domain counts, modal ratios and optional frequencies. A comparison returns congruent, spectra_differ or not_distinguished_at_this_resolution. Optional mode shapes describe the ideal numerical membrane.

Example MCP call

{
  "name": "hear_the_shape",
  "arguments": {
    "polygon": [
      [
        0,
        0
      ],
      [
        0.5,
        0
      ],
      [
        0.5,
        0.5
      ],
      [
        0,
        0.5
      ]
    ],
    "boundary": "fixed",
    "modes": 3,
    "wave_speed": 100,
    "include_mode_shapes": true
  }
}

Send this tool name and arguments through a connected MCP client. Discover the authoritative input schema with tools/list.

Call this engine in one command

Node.js 20+ and npm. This downloads a small remote MCP client; it does not install the engine locally.

npx --yes --package https://scorecompute.com/downloads/scorecompute-call-0.14.2.tgz scorecompute-call hear_the_shape --arguments '{"polygon":[[0,0],[0.5,0],[0.5,0.5],[0,0.5]],"boundary":"fixed","modes":3,"wave_speed":100,"include_mode_shapes":true}'

Client download, PowerShell input and verification →

Direct MCP access

hear_the_shape is independently callable. It is deliberately not connected to the automatic planner, so nothing passes its results to another engine for you. Two tools returning similar JSON fields does not mean their results are compatible.

Cite this engine

Version 0.1.0, source SHA-256 e355ad14fa23…. Evidence recorded on release 0.16.1; the public service currently runs 0.17.1. Replace the access date when you cite it.

ScoreCompute. Hear the shape of a polygonal drum (hear_the_shape), version 0.1.0, source SHA-256 e355ad14fa23b7d13b19fb01e1b052d7f2eedd1abcc652f993bc38b1245fa967. Evidence release 0.16.1, service release 0.17.1. https://scorecompute.com/engines/hear-the-shape/ (accessed YYYY-MM-DD).

All engine citations · Evidence card

Execution and availability

ScoreCompute exposes this tool through MCP Streamable HTTP. Rust computation runs on a connected worker; the public website and MCP gateway run separately. Among these 22 scientific tools, CUDA is implemented for simulate_pi; the other scientific engines run on CPU. The separate contributor network runs two compiled public workloads: a π estimate and fixed synthetic schedule probes. Requests are bounded and concurrent work may be refused when capacity is occupied.

Record inputs, assumptions and returned provenance when sharing a result. The public observatory displays software client names and tool activity, without publishing calculation arguments or results.

Explore another engine →Agent-readable overview ↗

Sources

These publications describe the method or a reference used in its tests. Citing them does not certify this implementation.

First published 1 October 2026 · Last updated 2 November 2026