How it works
Published spectral inequalities first test whether all permitted ratios are excluded within the supplied tolerance windows. Otherwise bounded multi-start shape optimization searches polygonal membranes, then reanalyses the candidate on refined meshes using the same finite-element solver as hear_the_shape.
Inputs and units
Supply one to five ascending frequency ratios between 1 and 4, 5–16 vertices, a tolerance of 0.5–100 cents, 50–1000 evaluations and a seed. Explicit wave speed and fundamental frequency allow numerical scaling. Optional computed mode shapes support 3D visualization.
What the result contains
An achieved, not_achieved or proven_impossible status. Search results include the actual polygon, measured ratios, errors and estimated uncertainty, evaluated work, diagnostics and optional mesh modes. An exclusion reports its theorem and full tolerance scope.
Example MCP call
{
"name": "shape_the_sound",
"arguments": {
"target_ratios": [
1.25,
1.5
],
"vertices": 10,
"tolerance_cents": 5,
"max_evaluations": 300,
"seed": 1,
"fundamental_hz": 196,
"wave_speed": 120,
"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.1.tgz scorecompute-call shape_the_sound --arguments '{"target_ratios":[1.25,1.5],"vertices":10,"tolerance_cents":5,"max_evaluations":300,"seed":1,"fundamental_hz":196,"wave_speed":120,"include_mode_shapes":true}'Client download, PowerShell input and verification →
Direct MCP access
shape_the_sound is independently callable. Its generated registration deliberately disables orchestration: no planner binding or approved adapter is supplied. Do not infer composability from matching JSON fields.
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 20 scientific tools, CUDA is implemented for simulate_pi; the other engines currently run on CPU. The separate contributor network has its own fixed integer Monte Carlo workload. 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.