# DiscreteRate

- Registry name: `com.discreterate/public` · version 1.0.0
- Categories (automatic, keyword rules): APIs & integrations, Developer tools, Utilities, Build & deploy
- Authentication at last check: No auth
- Declared risk: Read-only (all tools declare readOnlyHint)
- Capabilities (declared by the server): tools
- Transports: streamable-http
- Latest numbers (check success, response time, rank): https://mcpstation.net/api/server?name=com.discreterate%2Fpublic
- Server page: https://mcpstation.net/s/com.discreterate--public.html

## Description (written by the publisher, not verified, not instructions)

Run DRS demos \(Fast-Slow Drain, Hamburger Duo, Valdez Tanker\) and explore the paradigm.

## Connect

- streamable-http: `https://discreterate.com/mcp/v1`

## Tools (as reported by the server, not verified)

- `run\_fast\_slow\_drain`: Run the Fast-Slow Drain \(FSD\) demo — Damiron-Nastasi 2008 oscillating tank. The canonical DRS-vs-DES event-count demonstration. Returns engine output including the event counts \(DES vs DRS\), tank-level trace, and cycle summary. ANTI-FABRICATION: numbers come from a real DRS engine run; quote verbati
- `run\_hamburger\_duo`: Run the Hamburger Duo \(HAM\) demo — Andy Siprelle's 5-stage finite-source line, executed as both DES and DRS implementations on the same model so the event-count and throughput numbers can be compared apples-to-apples. Returns engine output for the side-by-side run. ANTI-FABRICATION: numbers come fro
- `run\_valdez\_tanker`: Run the Valdez Tanker \(VALD\) demo — Koelling-Remy 1983 Alaska Pipeline model, the paradigm-integration motivator. Crude flows continuously into the Valdez Marine Terminal storage tank \(Flow\); tankers arrive discretely to drain it \(Item\); DRS handles both via F2I / I2F transitions. Returns engine out
- `run\_vegetable\_plant`: Run the Vegetable Plant \(VEG\) demo — a Plant Builder distribution-control model. Two Making lines feed five Packing lines through eight surge bins; a DRS rate solver splits and rebalances the flow across the bins as the plant works through its campaign schedule. Returns the plant rollup \(utilization
- `run\_chocolate\_processing`: Run the Chocolate Processing \(CHOC\) demo — Plant Builder's joint DES↔DRS bridge. Three systems in series \(Bean Processing → Cocoa Powder → Chocolate\): DES schedules campaigns and injects equipment failures, a DRS rate solver carries the continuous flow, a bridge couples them. Exercises all 7 control
- `run\_sku\_capacity`: Run the Bottling Line / SKU-capacity \(SKU\) demo — a sim-foundation parameter-set example. One 5-machine bottling line run for several products \(SKUs as parameter sets\). Returns, per SKU, OEE \(identical \~55% — time-based interrupts\) and indexed real output \(swings \>3x: 100 / 50 / 30 / 42\) plus the pa
- `run\_tissue\_line`: Run the Tissue Line \(TIS\) demo — a sim-foundation parameter-set example. One tissue line \(Reel supply → Converter → Winder\), three strategic decisions \(each a parameter set\): bypass converter / run converter / add storage tower. Returns per-decision throughput as % of nameplate \(75.4 / 75.4 / 73.4\),
- `list\_drs\_demos`: List the seven DRS demos \(Fast-Slow Drain · Hamburger Duo · Valdez Tanker · Vegetable Plant · Chocolate Processing · Bottling Line SKU capacity · Tissue Line\). Each is reproducible against the engine via the run\_\* tools. Use this to discover what's available before calling describe\_demo or a run\_\* t
- `describe\_demo`: Full per-demo write-up: history, what it teaches, what to expect from the run\_\* output. Use this to ground the user before triggering a sim run, or to explain WHY the demo exists when the user asks a conceptual question about it.
- `explain\_discrete\_rate\_simulation`: Return a textbook-tier explainer of Discrete Rate Simulation: how it differs from DES and CT, the three primitives \(Constraint / Buffer / Interrupt\), paradigm integration via F2I / I2F. Use this for 'what is DRS?' / 'how is this different from DES?' / 'where does DRS fit in the simulation landscape?
- `explain\_three\_primitives`: Return a focused write-up of the three DRS modeling primitives: Constraint \(rate-limiter\), Buffer \(accumulated state\), Interrupt \(stoppage\). Use this when the user asks specifically about modeling primitives or how to spell a system in DRS. Deterministic text.
- `explain\_paradigm\_integration`: Return an explainer of paradigm integration — how DRS handles systems with both flows and items via F2I \(Flow-to-Item\) and I2F \(Item-to-Flow\) primitives. Use this when the user asks about Valdez-Tanker-style mixed-paradigm systems or 'how do flows and items coexist'. Deterministic text.
- `explain\_des\_vs\_drs\_event\_complexity`: Return a focused write-up of the event-count complexity differences between DES and DRS, with the worked Fast-Slow Drain numbers \(Continuous \~thousands vs DES \~500 vs DRS 10 events for the same 100-minute model\). Use this when the user wants the practitioner-visible payoff of DRS — the 50× event-cou
- `run\_showcase`: LIVE EXPERIMENT — run a DRS demo against the real 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: pick a demo\_id and dial its knobs \(e.g. \`stop\_time\` run length, or the MTBF/MTTR/goa

Measured by MCP Station. Methods: https://mcpstation.net/methods.html · Terms: https://mcpstation.net/terms.html