MCP server for building, simulating, and exporting Petri Net models for production and queueing systems. Exposes tools for creating networks, adding patterns, connecting components, optimizing networks, running simulations, and exporting to PNML format.
Critical failures across all dimensions. 7 of 9 tools have ZERO visible input schemas in source code (add_place, add_transition, add_arc, optimize_network, export_pnml, run_simulation, get_simulation_results show empty {} schemas). Descriptions exist but are generic and lack actionable guidance. No parameter descriptions visible for any tool. No output schemas documented. Error handling absent. Tool names lack clarity (e.g., 'show_chart' is ambiguous, is it display or generate?). This server cannot reliably guide LLM tool selection or parameter construction.
Add an arc (connection) between places and transitions in the Petri Net
Add a place (state node) to the Petri Net
Add a transition (event/activity node) to the Petri Net
Create a new empty Petri Net, clearing any previous network. Use this FIRST when user wants to build a new model from scratch.
Export the Petri Net to PNML (Petri Net Markup Language) format
Retrieve results from the last simulation run
Optimize the Petri Net by fusing redundant Transfer transitions
7 of 9 tools have empty input schemas ({}). Blocks LLM parameter construction entirely.
No parameter descriptions visible in source for any tool. LLMs cannot infer what 'name' means in create_network or what fields add_place/add_transition expect. Violates pattern:tool-description baseline (100% of A+ tools have param descriptions).
No output schemas documented. LLMs cannot plan downstream tool calls or extract required fields (e.g., what does run_simulation return? What fields does get_simulation_results expose?). Violates pattern:tool baseline (100% of A+ tools have documented return types).
Inferred effective spec: <=2025-11-25.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 42 | <=2025-11-25 | v2 |
Run a simulation of the Petri Net
Display a chart/graph inline in the chat. The frontend renders it visually. ALWAYS use this tool instead of ASCII art, text-based charts, or code snippets.
Ambiguous tool names. 'show_chart' does not clearly indicate whether it generates or displays. 'optimize_network' lacks context on what optimization means. Violates pattern:tool naming baseline (90% of A+ tools start with clear action verbs).
No error handling guidance. Tools provide no recovery hints, retryability classification, or actionable error messages. Violates pattern:recovery-guide and pattern:error-classification.