AI · Tools

Everything your assistant can do in 00 Simulator.

35 tools cover the whole job, from picking a driver to checking the build. These are the tools your assistant sees when it connects; it chooses which to call, and when, from what you ask.

  1. 1

    Pick a driver

    Search simulation-ready drivers by name or Thiele/Small filters, read one in full, and check a set of parameters for missing fields and contradictions.

    • search_drivers
    • get_driver
    • validate_driver
  2. 2

    Design

    Suggest a starting alignment, read the fields each enclosure type takes, then build and edit candidates in a workspace of your own.

    • suggest_enclosure
    • get_enclosure_schema
    • create_workspace
    • list_workspaces
    • get_workspace
    • add_enclosure
    • update_enclosure
    • update_workspace
  3. 3

    Simulate

    Run the solver on a saved version, including horns, EQ and multiple-entry drivers, and read the numbers back.

    • simulate_workspace
    • get_simulation_results
  4. 4

    Show you

    Draw graphs in the conversation, arrange the dashboard in your open tab around what is being explained, and mark the frequencies worth looking at.

    • render_simulation_graphs
    • show_graphs
    • annotate_graphs
  5. 5

    Check the build

    Bring in a real measurement, such as a REW export, link it to the design it measures, and compare the two: the level difference and the shape difference are reported separately.

    • import_trace
    • compare_trace
    • list_traces
    • get_trace
    • update_trace
    • delete_trace
  6. 6

    Keep or undo

    Finish with a summary you can undo in one go, restore any saved version, and clear away the candidates and workspaces that did not work out.

    • end_workspace_session
    • list_workspace_revisions
    • get_workspace_revision
    • restore_workspace_revision
    • remove_enclosure
    • delete_workspace

Appearance:Build an app theme for you, for instance more contrast between the side-panel sections, check it against the contrast floors, and switch to it when you ask.get_theme_schemalist_themesget_themesave_themeactivate_themedelete_theme

Its own limits:List the workspace operations this connection allows and the permission each one needs.list_workspace_capabilities

Live in the simulator

It works where you can see it.

Open a workspace, then ask. What your assistant does shows up in that tab as it happens, and you can step in at any point.

  • Its edits land as they happen

    Each change it saves is applied in place as one undo step. Your own design edits wait while it writes, and Take control ends that at once.

  • The graphs behind its answer

    It brings the graphs its numbers come from to the front, the main one largest. Keep that arrangement, or go back to your own layout.

  • Marks on the curves

    Bands, lines, levels and points, numbered to match what it says. They stay until the design changes, and you can keep one as a note or clear it.

  • A quiet handback

    When it finishes, a small notification says what changed. Undo puts it all back and restores your layout; closing it keeps the lot.

Not watching?

Graphs come to the chat.

Nothing needs to be open. In clients that support MCP Apps, such as ChatGPT, the assistant draws up to six graphs right in the conversation, and you can change the power or the EQ there and apply it to the design.

  • SPL
  • Max SPL
  • Impedance
  • Phase
  • Group delay
  • Excursion
  • PR excursion
  • Port velocity
  • Rear port velocity
  • Apparent power
  • Current draw

Everywhere else the same run comes back as numbers, and the 26 graph tiles in the app show the rest.

Where the numbers come from

Every number comes from the solver.

A language model recalling a driver’s parameters, or sizing a box from a rule of thumb, is how you get a confident wrong answer. Connected here, your assistant looks things up, runs the simulator, and can check the result against your own measurement.

  • The app’s own solver

    Across 50 WinISD projects, 93% of comparison points agree within tolerance, and 122 Hornresp captures cover 8 horn families. Every deviation is published.

    See the validation

  • 674 simulation-ready drivers

    search_drivers and get_driver read the simulator’s built-in library, so the parameters are the ones the solver uses. validate_driver checks a set you paste in for missing fields and contradictions.

  • Your measurements

    Import a REW export and compare_trace separates a level offset, from distance or drive, from a real difference in shape. The assistant reports both instead of judging a picture.

One URL, a sign-in, and your assistant has all of this.

Watch it workSet it up