openisd-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_driversA | Search the OpenISD driver library (1600+ woofers/subs, from WinISD .wdr files) by brand/model keywords. Returns matching drivers with key T/S params and the |
| get_driverA | Load a library driver: full T/S parameters (friendly units) plus upstream validation issues. Warns (e.g. Xmax undefined) do not block — they only omit reference lines. |
| design_boxA | Compute an enclosure for a driver: sealed from a target Qtc (default 0.707 Butterworth) or vented from the QB3/Thiele alignment (Vb, Fb, port dimensions). Includes EBP suitability advice. Returns simulateParams ready to pass to simulate. |
| simulateB | Run the OpenISD Thiele-Small engine on a design: SPL curve (~60 points), F3, Qtc/Fc or Fb, max SPL and its limiter (Xmax vs power), excursion and impedance peaks. Degenerate designs (NaN curves) are rejected before returning. Supports HP/LP/Linkwitz/peaking filters for subsonic protection, etc. |
| add_driverA | Add a custom driver to the library. Takes T/S params (friendly units), writes a WinISD-compatible .wdr using upstream's exporter, and makes it searchable immediately. Returns the library |
| evaluate_designA | Full design evaluation: runs design_box + simulate + automated PASS/WARN/FAIL checklist in one call. Checks: Qtc/Fb alignment, excursion margin vs Xmax, port velocity/chuffing (Mach ≤5%), F3 extension, SPL limiter, impedance peak, box volume sanity. Returns overall verdict + detailed checks with thresholds. Supports filters for subsonic protection. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 6 tools
Each tool has a clearly distinct purpose: searching, loading, designing, simulating, adding, and evaluating. There is no overlap or ambiguity in what each tool does.
Most tools follow a verb_noun pattern (e.g., search_drivers, get_driver, design_box, add_driver, evaluate_design). The single exception is 'simulate', which is a bare verb but still clear and consistent in style.
Six tools cover the core workflow of speaker design (search, load, design, simulate, add, evaluate) without bloat. Each tool earns its place and the set feels well-scoped for the server's purpose.
The surface covers the main lifecycle: discovery, loading, design creation, simulation, custom additions, and full evaluation. Minor gaps exist (e.g., no update or delete for drivers), but these are non-essential and the core domain is well covered.