DiscreteRate
Server Details
Run DRS demos (Fast-Slow Drain, Hamburger Duo, Valdez Tanker) and explore the paradigm.
- Status
- Healthy
- Uptime
- 100.0% over the last 24 hours
- Last Tested
- Transport
- Streamable HTTP · MCP 2025-06-18
- URL
- ChatGPT
- –
- Claude
- –
TDQS
Scored across 14 tools
The run_* tools each target a distinct named demo, and the overlap risk between run_showcase and the curated run_* tools is explicitly resolved in the description (live parameterized experiment vs. canonical reference numbers). The four explain_* tools are also scoped to distinct questions, though explain_discrete_rate_simulation overlaps somewhat with explain_three_primitives and explain_des_vs_drs_event_complexity since it covers the primitives and DES comparison too.
The set follows a clean verb_noun convention with coherent prefixes (explain_*, run_*, list_*). Minor deviations: describe_demo lacks the domain qualifier its sibling list_drs_demos carries, and run_showcase breaks the run_<demo_id> pattern used by the other six runners, so its role must be inferred from the description rather than the name.
14 tools is well inside the healthy range and every tool earns its place: one runner per demo (7), a discovery tool, a deep-dive tool, four conceptual explainers, and one parameterized live-run tool. No redundant wrappers or filler.
All seven demos listed by list_drs_demos have a dedicated run_* tool, and the explain/describe layer covers the conceptual surface, so the lifecycle from discovery to execution to explanation is closed. Minor gap: nothing documents the tunable knobs/parameter schema per demo for run_showcase, and there is no way to compare two runs or retrieve prior results.
Available Tools
14 toolsdescribe_demoDescribe one DRS demoARead-onlyIdempotentInspect
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.
Inputs: demo (required).
explain_des_vs_drs_event_complexityDES vs DRS event-count primerARead-onlyIdempotentInspect
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-count reduction at the boundary-transition layer. Deterministic text.
Inputs: no named parameters.
explain_discrete_rate_simulationDRS paradigm primerARead-onlyIdempotentInspect
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?' style questions. Deterministic text — no engine call, no RNG.
Inputs: no named parameters.
explain_paradigm_integrationF2I / I2F integration primerARead-onlyIdempotentInspect
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.
Inputs: no named parameters.
explain_three_primitivesThree primitives primerARead-onlyIdempotentInspect
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.
Inputs: no named parameters.
list_drs_demosList DRS canonical demosARead-onlyIdempotentInspect
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_* tool.
Inputs: no named parameters.
run_chocolate_processingRun Chocolate Processing (Plant Builder DES↔DRS bridge)ARead-onlyIdempotentInspect
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 controllers + Goal blocks. Returns the plant rollup (schedule occupancy vs busy utilization, total downtime, campaigns), per-product attainment, and per-system campaign timelines with downtime. ANTI-FABRICATION: numbers come from a real Plant Builder engine run; quote verbatim.
Inputs: no named parameters.
run_fast_slow_drainRun Fast-Slow Drain (Damiron-Nastasi 2008)ARead-onlyIdempotentInspect
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 verbatim, don't recall from training data.
Inputs: simulation_minutes.
run_hamburger_duoRun Hamburger Duo (Siprelle, DES + DRS side-by-side)ARead-onlyIdempotentInspect
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 from a real engine run; quote verbatim.
Inputs: simulation_days.
run_showcaseRun a DRS demo live (your parameters)ARead-onlyInspect
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/goal knobs on the plant demos) to see the real numbers for that exact configuration. IMPORTANT: a run_showcase result is NOT a verified reference number — unlike the run_* tools (run_fast_slow_drain / run_hamburger_duo / run_valdez_tanker / run_vegetable_plant / run_chocolate_processing), which return curated, canonical reference values. Present run_showcase output as a live experiment result for the parameters passed; don't blend it with the curated reference numbers. Quote any figures verbatim; do not round, average, or derive.
Inputs: demo_id (required), knobs.
run_sku_capacityRun Bottling Line SKU capacityARead-onlyIdempotentInspect
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 pacing machine. Shows you can't read per-SKU capacity off OEE. ANTI-FABRICATION: numbers come from a real sim-foundation engine run (indexed/anonymized); quote verbatim.
Inputs: no named parameters.
run_tissue_lineRun Tissue Line strategic decisionARead-onlyIdempotentInspect
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), the binding bottleneck (the upstream parent-reel supply in all three), and converter/storage detail. Shows the downstream decision barely moves throughput — invest at the constraint. ANTI-FABRICATION: numbers come from a real sim-foundation engine run (indexed/anonymized); quote verbatim.
Inputs: no named parameters.
run_valdez_tankerRun Valdez Tanker (Koelling-Remy 1983)ARead-onlyIdempotentInspect
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 output including tanker arrival/departure events and tank-level trace. ANTI-FABRICATION: numbers come from a real engine run; quote verbatim.
Inputs: simulation_days.
run_vegetable_plantRun Vegetable Plant (Plant Builder distribution control)ARead-onlyIdempotentInspect
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, campaigns, active window), per-product goal attainment, per-system campaign timelines, and final surge-bin / delivered levels. ANTI-FABRICATION: numbers come from a real Plant Builder engine run; quote verbatim.
Inputs: no named parameters.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Related MCP Connectors
Demo personal-finance MCP App: spending, subscriptions, and net worth as interactive UI.
Conversational what-if simulation: build, diagnose and compare Petri-net models; CC0 catalog.
Plan, run and inspect AI-agent drills with synthetic users, hosted tools and cloud worlds.
SWAT+ watershed models for any river in the lower 48 states, with groundwater and PFAS data
Related MCP Servers
- AlicenseNot gradedqualityBmaintenanceRuns 19 simulated form-mode and URL-mode elicitation scenarios against a mock MCP server and client, exposing the raw JSON-RPC of every message, rendering the dialog a compliant client must show, and flagging MUST/SHOULD violations. Everything stays in-process and offline, so users can study consent, secret handling, retries, phishing, and broken-server behaviour without touching a real network.MIT
- AlicenseAqualityDmaintenanceDemonstrates MCP capabilities through 8 runnable demos including tools, resources, and bidirectional communication, covering patterns like polite CLI, OAuth handoff, async progress, and shared UI artifacts.164MIT
- AlicenseNot gradedqualityDmaintenanceHosts six official Model Context Protocol MCP Apps examples as remote Streamable HTTP MCP servers you can try by URL without cloning or local setup.Apache 2.0
- AlicenseNot gradedqualityDmaintenanceA comprehensive testing suite demonstrating all Model Context Protocol (MCP) Apps features through interactive Weather Dashboard and 3D Globe viewer applications.MIT
Glama MCP Gateway
Add one secure layer between your agents and this server.