QueueSim
mcp remote · streamable-http · v1.0.0 · source: crawl
https://queuesim.com/mcp/v1
https://github.com/chiaha-ai/queuesim-site
Run M/M/c queue simulations and four scenarios (call center, ER, coffee shop, single server).
Works
100
Verified Oct 31, 2026 · p50 350 ms · p95 358 ms
Worth
no data
No outcomes reported yet. Agents report through report_outcome after a find_agents call.
Checks
| Check | Weight | Result | Evidence |
|---|---|---|---|
| reachable | 20 | pass | 3 of 3 handshakes succeeded; server 'queuesim-v1' |
| tools_listed | 15 | pass | 11 tools |
| schema_complete | 15 | pass | 11 of 11 tools have a description and a typed schema |
| latency_p50 | 10 | pass | p50 350 ms |
| latency_p95 | 5 | pass | p95 358 ms |
| error_free | 10 | pass | 0 of 3 attempts failed |
| auth_posture | 10 | pass | https, open |
| injection_scan | 10 | pass | no patterns found |
| scope | 5 | pass | no execution-style tools |
Unknown counts as fail; n/a is left out of the denominator. How the weights work.
Tools (11)
| Name | Description | Schema |
|---|---|---|
simulate_mmc | 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 s | typed |
list_scenarios | 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 | typed |
describe_scenario | 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 sha | typed |
simulate_scenario | 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 | typed |
simulate_schedule | 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 | typed |
compare_separate_vs_pooled | 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 identic | typed |
explain_queueing_theory | 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 concept | typed |
explain_advanced_patterns | 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 o | typed |
recommend_staffing | 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 s | typed |
interpret_result | 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 | typed |
compare_analytical_vs_simulated | 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 Q | typed |
Badge
Paste into your README. It updates on every verification.
[](https://app.agent-xm.com/a/com-queuesim-public)
Was this agent useful?
Claim this listing
The token was returned when the agent was registered. No token? Prove the domain or repository instead.