com.reliasim/public

Official8 tools

ReliaSim

Reliability and bottleneck simulation for manufacturing lines; run experiments, sweep buffers.

Simulate manufacturing reliability, bottlenecks, and buffer optimization experiments.

Captured live from the server via tools/list.

find_bottleneck

Single Run bottleneck analysis for the selected chapter — which node has the worst availability, per-interrupt downtime split, throughput, OEE. All eight chapters return verified dys-cli sales-prototype numbers. ANTI-FABRICATION: numbers in the response are canonical reference values from real dys-cli engine runs. Quote them VERBATIM. Do not round, estimate, or recall from training data. For follow-ups about the same chapter, re-call this tool.

Parameters (1)

chapterstring
Which curriculum chapter the tool should answer about. Format: `bs<1-5>-<ct|leds>`. Both tracks run on the same real plant data — `ct` = Constraint-Level (interrupts rolled up to one Weibull per machine, 5 total) and `leds` = LEDS-Level (interrupts drilled down to named failure modes, 36 total). Defaults to bs1-ct when omitted.

get_chapter_facts

Structural facts of the selected chapter — topology, rate limits, interrupt distributions, expected efficiency. Use when the user asks about the line's configuration. ANTI-FABRICATION: rates and distributions are verified .aidos-file values. Quote VERBATIM; do not estimate or substitute training-data recall.

Parameters (1)

chapterstring
Which curriculum chapter the tool should answer about. Format: `bs<1-5>-<ct|leds>`. Both tracks run on the same real plant data — `ct` = Constraint-Level (interrupts rolled up to one Weibull per machine, 5 total) and `leds` = LEDS-Level (interrupts drilled down to named failure modes, 36 total). Defaults to bs1-ct when omitted.

get_chapter_narrative

Long-form narrative for the selected chapter — what the chapter adds to the complexity ladder and the key teaching point. Use when the user asks 'walk me through this' or wants the conceptual primer. Pure prose, no numerical claims; safe to summarize.

Parameters (1)

chapterstring
Which curriculum chapter the tool should answer about. Format: `bs<1-5>-<ct|leds>`. Both tracks run on the same real plant data — `ct` = Constraint-Level (interrupts rolled up to one Weibull per machine, 5 total) and `leds` = LEDS-Level (interrupts drilled down to named failure modes, 36 total). Defaults to bs1-ct when omitted.

run_gain_loss

Gain/Loss experiment — disable each interrupt one at a time, measure production recovered. Reveals the ACTUAL impact of each failure mode (Gain ≠ Loss: removing one lets others fire more often). Available on `bs1-leds`, `bs3-leds`, `bs4-ct`, `bs4-leds`. Use when the user asks 'what if we fixed X?' / 'which interrupt matters most if we actually fixed it?' / 'show me the Pareto'. ANTI-FABRICATION: per-interrupt recovered-production numbers come from real dys-cli runs. Quote VERBATIM; the Gain ≠ Loss interaction is exactly the kind of figure LLMs are prone to fabricate — don't.

Parameters (1)

chapterstring
Which curriculum chapter the tool should answer about. Format: `bs<1-5>-<ct|leds>`. Both tracks run on the same real plant data — `ct` = Constraint-Level (interrupts rolled up to one Weibull per machine, 5 total) and `leds` = LEDS-Level (interrupts drilled down to named failure modes, 36 total). Defaults to bs1-ct when omitted.

run_buffer_tradeoff

Buffer Tradeoff experiment — sweep a buffer's capacity from 50 → 10,000 units, measure throughput gain. Shows the diminishing-returns elbow for buffer sizing. Only defined on `bs4-ct` and `bs4-leds`; each chapter has THREE inline buffers with different placements (pass `buffer` id to pick one). Compare CT vs LEDS on the same slot to see why interrupt-detail level changes buffer ROI math (e.g. b3: CT +23.7% vs LEDS +64.2%). Use when the user asks 'how big should the buffer be?' / 'do buffers help on this line?' / 'which buffer position gives the most gain?' / 'what's the diminishing-returns point?'. ANTI-FABRICATION (CRITICAL): the specific tradeoff numbers (e.g. CT +23.7% vs LEDS +64.2%) are sweep-derived reference values. Quote VERBATIM in your reply; do NOT recall similar percentages from training data — every buffer position has different math.

Parameters (2)

chapterstring
Chapter id. Only `bs4-ct` and `bs4-leds` have buffer tradeoffs defined.
bufferstring
Buffer id to sweep. The Buffer-Options Constraint-Level model has `b3` (Buffer 1, between Capper↔Labeler), `b4` (Buffer 2, between Labeler↔Case Packer), `b5` (Buffer 3, between Case Packer↔Palletizer). The Buffer-Options LEDS model has `b2` (Buffer Option 1, earliest), `b3` (Buffer Option 2, middle), `b4` (Buffer Option 3, last). Defaults to b3 if omitted — but pick the buffer that matches the question (e.g. 'the first inline buffer' = b3 on CT, b2 on LEDS).

explain_concept

Definitional primer for ReliaSim's framework concepts — Constraint, Buffer, Interrupt, Converter, cascading losses, OEE, Gain/Loss methodology, Buffer Tradeoff. Returns bundled theory content, NOT interpretation of any specific simulation run. Use for 'what is X?' / 'how does X work?' / 'explain the framework' questions. For line-specific claims (throughput, availability, what-if), call the sim tools instead.

Parameters (1)

conceptstringrequired
Which concept to explain. Returns a definitional primer — theory, not interpretation of a specific simulation run. Use for 'what is a Constraint?' / 'what are cascading losses?' / 'explain Gain-Loss'.

compare_chapters

Side-by-side comparison of two chapters — tracks, topology, OEE, throughput, headline bottleneck. Output is sim-derived (no interpretation drift). Use for 'how does X compare to Y?' / 'what's the difference between Constraint-Level and LEDS-Level on the same model?' / 'what changes when we add buffers?' questions. ANTI-FABRICATION: per-chapter OEE/throughput numbers are real reference values; the side-by-side delta is computed from them, not estimated. Quote VERBATIM.

Parameters (2)

chapter_astringrequired
First chapter id (left column of the comparison). Defaults to bs1-ct.
chapter_bstringrequired
Second chapter id (right column of the comparison). Defaults to bs1-leds — same plant data as bs1-ct, but with interrupts drilled down to named failure modes; the canonical first-look comparison.

run_showcase

LIVE experiment — run a bottling-line demo against the real ReliaSim engine with parameters you choose, and get its verbatim run envelope (metadata, execution stats, metrics, details). This is the only tool that COMPUTES fresh output: dial `duration_days` (or buffer capacities on the bs4 demos) and see the real numbers for that exact configuration. IMPORTANT: a run_showcase result is NOT a verified reference number — it is live output for the parameters you passed. Label it as an experiment result, not a canonical figure, and don't blend it with the curated reference numbers. For the canonical, verified OEE/throughput/bottleneck values use find_bottleneck / run_gain_loss / run_buffer_tradeoff instead. Quote any figures verbatim; do not round, average, or derive.

Parameters (2)

demo_idstringrequired
Which bottling-line demo to run live. Same eight ids as the curated tools (bs1-ct … bs4-leds).
knobsobject
Optional parameters as a map of name:number. All eight demos accept `duration_days` (run length, 7–90 days). The two Buffer-Options demos also accept buffer capacities: bs4-ct → `buffer_capacity_b3` / `buffer_capacity_b4` / `buffer_capacity_b5`; bs4-leds → `buffer_capacity_b2` / `buffer_capacity_b3` / `buffer_capacity_b4` (each 0–10000 units). Unknown names are rejected; out-of-range values are clamped to the allowed range by the engine.

Install

claude_desktop_config.json

{
  "mcpServers": {
    "public": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://reliasim.com/mcp"
      ]
    }
  }
}

Desktop config is stdio-only; this bridges via mcp-remote. Native remote: Settings > Connectors.