{"id":"com.queuesim/public","slug":"com-queuesim-public","title":"QueueSim","description":"Queueing simulation: M/M/c, staffing, Erlang C checks, and multi-step models built from nodes.","version":"1.3.0","publisher":{"kind":"domain","id":"queuesim.com","label":"queuesim.com","url":"https://queuesim.com"},"website":"","repository":"https://github.com/chiaha-ai/queuesim-site","remotes":[{"type":"streamable-http","url":"https://queuesim.com/mcp/v1"}],"packages":[],"published":"2026-11-10","updated":"2026-11-10","status":"online","auth":"","latency_ms":914,"checked":"2026-11-19","uptime":100,"checks":3,"tools":[{"name":"simulate_mmc","title":"Run M/M/c queue simulation","description":"Run a generic M/M/c queue simulation. Provide an arrival rate (λ, arrivals/hour), a service rate per server (μ, customers/hour each server can finish), and a server count (c). Optional: distribution shapes, service coefficient of variation, run length. Returns per-hour metrics and an overall summary (avg wait, queue length, offered load, throughput). This is the primary tool for 'how many servers ","read_only":true},{"name":"list_scenarios","title":"List preset scenarios","description":"List the four pre-built QueueSim scenarios. Returns key, title, and one-line description for each (Single Server, Coffee Shop, Grocery Checkout, Call Center). Call this when the user's problem matches one of the preset shapes — use describe_scenario for more detail and simulate_scenario to run one.","read_only":true},{"name":"describe_scenario","title":"Describe preset scenario","description":"Return full details for one preset scenario: title, description, teaching note, peak parameters, and per-hour arrival + staffing arrays. Use this before simulate_scenario to understand the default shape and what overrides make sense.","read_only":true},{"name":"simulate_scenario","title":"Run preset scenario","description":"Run one of the four preset scenarios (single, coffee, grocery, callcenter) with optional overrides. Overrides apply UNIFORMLY across open hours — e.g. setting servers=5 on 'coffee' replaces the 4/6/4 staffing pattern with a flat 5 during open hours (closed hours stay at zero). Use this for (a) faithful reproduction of a scenario's defaults, or (b) uniform scaling (everywhere it was open, use these","read_only":true},{"name":"simulate_schedule","title":"Run a custom 24-hour schedule simulation","description":"Run a queueing simulation against an arbitrary 24-hour staffing schedule. Take this when the user describes a custom day shape that doesn't match a preset (e.g., 'my coffee shop is open 6am–10pm with 4 baristas off-peak, 7 at the 8am rush, 5 at the 4pm rush'). Inputs: `arrivalRates` (24-element array of customers/hr per hour-of-day) and `staffing` (24-element array of servers/hr); optional uniform","read_only":true},{"name":"compare_separate_vs_pooled","title":"Compare pooled (M/M/c) vs separate (c × M/M/1) queueing","description":"Run the classic operations-research teaching demo: pooled queueing (one shared queue, c servers) vs separate queues (c independent queues, one server each, λ/c traffic to each). Both runs have identical total capacity (c × μ) and identical total arrivals (λ), so the offered load ρ is the same; the only structural difference is whether arrivals share a queue or split into c isolated streams. The po","read_only":true},{"name":"explain_queueing_theory","title":"Queueing theory primer","description":"Return a ~500-word educational explainer of M/M/c queueing theory: Little's Law, utilization, why averages mislead, how simulation relates to Erlang-C. No inputs. Use this when the user asks a conceptual 'why' or 'how does this work' question rather than asking for a number.","read_only":true},{"name":"explain_advanced_patterns","title":"Advanced patterns primer","description":"Return a textbook-level description of six queueing complexity patterns beyond basic M/M/c: abandonment/reneging, priority tiers, overflow routing, skills-based routing, compound service, and server outages. Use this when the user describes real-world complexity (customers hanging up, VIP queues, specialist escalation, agent breaks, transfers) that plain M/M/c doesn't model. The tool frames each p","read_only":true},{"name":"recommend_staffing","title":"Recommend minimum staffing for a wait-time target","description":"INVERSE of simulate_mmc — given an arrival rate, service rate, and a target average wait time, returns the SMALLEST number of servers needed to meet the target. Use this when the user asks 'how many servers do I need?' / 'what staffing keeps wait under N minutes?'. The tool runs a binary search over candidate server counts (up to maxServers, default 50), invoking the simulator for each candidate. ","read_only":true},{"name":"interpret_result","title":"Interpret M/M/c result","description":"Given an M/M/c configuration (arrivalRate, serviceRate, servers) and optionally an observed average wait, returns a queueing-theory framed interpretation: where you sit on the utilization curve, what ρ means in plain language, what one more or fewer server would qualitatively do, and which complexity factors (priority, abandonment, skills routing) might be hiding in real data the M/M/c model can't","read_only":true},{"name":"compare_analytical_vs_simulated","title":"Compare closed-form Erlang-C vs DES simulation","description":"Run the same M/M/c configuration through BOTH the closed-form Erlang-C formula AND the discrete-event simulator, returning a side-by-side comparison with deltas. Use this when the user is validating QueueSim's engine against textbook values, learning queueing theory by watching simulation converge on the formula, or auditing a result that 'feels off' — agreement within ~5% is the canonical sanity ","read_only":true},{"name":"queue_model_guide","title":"QueueSim Cloud model guide","description":"How to build a QueueSim Cloud model: the node types (arrivals, service, delay, split, settype, bytype, exit), staff groups, distributions, plan limits and a worked example. Call this before check_queue_model or run_queue_model when the user's system has more than one step (several stations in a row, shared staff, routing by percent or customer type, priority customers, people who give up or are tu","read_only":true},{"name":"check_queue_model","title":"Check a QueueSim Cloud model","description":"Check a QueueSim Cloud model (a multi-step queueing system built from nodes and staff groups) without running it. Returns every problem found (missing links, a line that would grow without limit, plan limits) tied to the node it is about, and a link that opens the model in QueueSim Cloud. Free plan: up to 8 nodes, 3 staff groups, 30 days, 1 run.","read_only":true},{"name":"run_queue_model","title":"Run a QueueSim Cloud model","description":"Run a QueueSim Cloud model (a multi-step queueing system built from nodes and staff groups) on the QueueSim Cloud discrete event engine. Returns, per service node: customers joined, served, gave up and turned away, mean and percentile waits in minutes and service levels; per staff group: utilization and busy staff; per exit: count and time in system. Also returns a link that opens the model in Que","read_only":true}],"server_info":{"name":"queuesim-v1","title":"QueueSim","version":"1.0.1","websiteUrl":"https://queuesim.com/claude"},"category":"agents","tags":["analytics"],"kind":"remote","source":"registry","submitted":{},"first_party":true,"domain_rank":null,"score":100,"indexable":true,"first_seen":"2026-04-25","stars":0,"badges":[],"sponsor":null,"page":"https://agentsindex.org/agents/com-queuesim-public/"}