← All engines

RUST ENGINE / shape_the_sound

Design a polygonal drum for a chord

Ask Rust to find an ideal fixed-edge membrane matching requested frequency ratios, then inspect its computed shape, vibrations and numerical limits.

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

What does a real call return?

For target ratios 1.25 and 1.5 within 5 cents, the search returned achieved, with ratios 1.2496 (-0.50 cents) and 1.4991 (-1.07 cents).

Recorded on 2 November 2026 through the public MCP endpoint, service release 0.17.1. Inputs and full responses, response SHA-256 012ff0d64aa5…. 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

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.2.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. 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.3.0, source SHA-256 609ea0dd8923…. Evidence recorded on release 0.16.1; the public service currently runs 0.17.1. Replace the access date when you cite it.

ScoreCompute. Design a polygonal drum for a chord (shape_the_sound), version 0.3.0, source SHA-256 609ea0dd8923ea9c464c925fe4437a81cd8a889be77d9f4f7139866fa9d92b91. Evidence release 0.16.1, service release 0.17.1. https://scorecompute.com/engines/shape-the-sound/ (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 4 October 2026 · Last updated 2 November 2026