Endpoints: 28,729MCP servers: 18,413Payout addresses: 2,070Paid calls: 1,526Letters: 13Defects: 1,322counted 1 min ago
teppi

Server definition

Hash
sha256:c1807523be2ba9d2f3e10fdcd0c8804a8f151cf7a04400da45bd27d8f6909b61
What it is
What a remote MCP server returned when asked what it offers: 14 tools

The blob, as servednamed by its sha256

{ "instructions": "DiscreteRate's public MCP. Two kinds of tool: (1) VERIFIED-REFERENCE tools — the seven run_* sim tools (Fast-Slow Drain, Hamburger Duo, Valdez Tanker, Vegetable Plant, Chocolate Processing, Bottling Line SKU capacity, Tissue Line) return canonical curated numbers from real DRS engine runs, and five explain_*/catalog tools return educator-flavored prose. (2) run_showcase (present only when the live engine is wired in) runs the real engine LIVE for parameters you choose and returns its verbatim run envelope — real output for that exact configuration, NOT a canonical reference number. ANTI-FABRICATION: quote every returned number verbatim; do not round, estimate, average, or recall figures from training data. Keep the two contracts distinct — present run_showcase output as a live experiment result and the run_* tools' numbers as canonical reference; never blend them. For a follow-up about a run you did earlier, re-call the tool rather than recalling numbers from chat history.", "tools": [ { "description": "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.", "inputSchema": { "properties": { "demo": { "description": "Which DRS demo to act on. See list_drs_demos for the catalog.", "enum": [ "fast_slow_drain", "hamburger_duo", "valdez_tanker", "vegetable_plant", "chocolate_processing", "sku_capacity", "tissue_line" ], "type": "string" } }, "required": [ "demo" ], "type": "object" }, "name": "describe_demo", "outputSchema": null }, { "description": "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.", "inputSchema": { "properties": {}, "type": "object" }, "name": "explain_des_vs_drs_event_complexity", "outputSchema": null }, { "description": "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.", "inputSchema": { "properties": {}, "type": "object" }, "name": "explain_discrete_rate_simulation", "outputSchema": null }, { "description": "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.", "inputSchema": { "properties": {}, "type": "object" }, "name": "explain_paradigm_integration", "outputSchema": null }, { "description": "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.", "inputSchema": { "properties": {}, "type": "object" }, "name": "explain_three_primitives", "outputSchema": null }, { "description": "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.", "inputSchema": { "properties": {}, "type": "object" }, "name": "list_drs_demos", "outputSchema": null }, { "description": "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.", "inputSchema": { "properties": {}, "type": "object" }, "name": "run_chocolate_processing", "outputSchema": null }, { "description": "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.", "inputSchema": { "properties": { "simulation_minutes": { "default": 100, "description": "Total simulation horizon in minutes. Default 100. Range 10-1000.", "maximum": 1000, "minimum": 10, "type": "integer" } }, "type": "object" }, "name": "run_fast_slow_drain", "outputSchema": null }, { "description": "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.", "inputSchema": { "properties": { "simulation_days": { "default": 7, "description": "Days to simulate. Default 7. Range 1-30.", "maximum": 30, "minimum": 1, "type": "integer" } }, "type": "object" }, "name": "run_hamburger_duo", "outputSchema": null }, { "description": "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.", "inputSchema": { "properties": { "demo_id": { "description": "Which DRS demo to run live against the real engine.", "enum": [ "fast_slow_drain", "hamburger_duo", "valdez_tanker", "vegetable_full", "chocolate_processing" ], "type": "string" }, "knobs": { "description": "Optional parameters as a map of name:number. fast_slow_drain / hamburger_duo accept `stop_time` (run length in minutes, 1–100000). valdez_tanker accepts `duration_days` (run length in days, 1–365; it drives the circulating-ship items loop). vegetable_full accepts `making_goal` (units, 0–100000), `making_mtbf` / `making_mttr` / `packing_mtbf` / `packing_mttr` (hours, 0–1000). chocolate_processing accepts `bp_goal` (units, 0–100000), `breaker_mtbf` / `breaker_mttr` (hours, 0–1000), `changeover_delay` (hours, 0–48). Unknown names are rejected; out-of-range values are clamped by the engine.", "type": "object" } }, "required": [ "demo_id" ], "type": "object" }, "name": "run_showcase", "outputSchema": null }, { "description": "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.", "inputSchema": { "properties": {}, "type": "object" }, "name": "run_sku_capacity", "outputSchema": null }, { "description": "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.", "inputSchema": { "properties": {}, "type": "object" }, "name": "run_tissue_line", "outputSchema": null }, { "description": "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.", "inputSchema": { "properties": { "simulation_days": { "default": 30, "description": "Days to simulate. Default 30. Range 1-90.", "maximum": 90, "minimum": 1, "type": "integer" } }, "type": "object" }, "name": "run_valdez_tanker", "outputSchema": null }, { "description": "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.", "inputSchema": { "properties": {}, "type": "object" }, "name": "run_vegetable_plant", "outputSchema": null } ] }
Verify it yourselfcurl -s https://api.teppi.xyz/v1/evidence/sha256:c1807523be2ba9d2f3e10fdcd0c8804a8f151cf7a04400da45bd27d8f6909b61 | sha256sum