A multi-paradigm simulation engine that supports Discrete-Event Simulation (DES) with SimPy and System Dynamics (SD) with PySD. Features advanced Model Builder tools for iterative, conversational model development. Integrates with LLMs through the Model Context Protocol (MCP) to enable sophisticated simulation capabilities in natural language environments.
This server demonstrates moderate quality with mixed strengths and gaps. Tools are properly registered with FastMCP and include parameter schemas with types. Descriptions are generally present and substantive (tool descriptions range 50-500+ chars), which is above the baseline. However, parameter descriptions are inconsistent, many lack detail about constraints, formats, or valid value ranges. Output schemas are not formally documented in the code, and error handling is basic. The server follows a clear verb_noun naming convention (simulate_*, save_*, load_*, export_*, list_*, validate_*) which is strong. Most tools accept well-scoped parameters (dict configs, enums for formats), but validation feedback and recovery guidance are limited. The comprehensive docstrings in simulate_des with examples and quick-start patterns show deliberate LLM optimization, but this rigor is not applied uniformly across all tools.
Export simulation model as formatted JSON for copy-paste to new conversations.
Get comprehensive schema documentation and examples for any simulation type.
List available simulation templates with filtering and search capabilities.
Load saved simulation model or list available models with filtering capabilities.
Load a simulation template by ID or name for model development.
Save simulation model with metadata for iterative development across conversations.
Advanced discrete-event simulation with comprehensive schema validation and SimPy integration.
Output schemas are not formally documented. Tools return dicts with structure inferred from docstrings, but LLMs cannot parse unstructured descriptions to understand response field types and nesting. This violates the requirement that 100% of A-tier tools have documented return types.
Parameter descriptions often lack constraint clarity. For example, load_model.schema_type and list_templates.complexity reference enum values ('DES', 'SD', 'basic', 'intermediate', 'advanced') in descriptions but do not define them as JSON Schema enums. This forces LLMs to guess valid values from text parsing, inviting hallucination.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-22 | D | 59 | 2026-07-28+ | v2 |
| 2026-03-09 | F | 35 | - | v1 |
Advanced System Dynamics simulation using PySD-compatible JSON format.
Validate simulation model JSON against appropriate schema with LLM-optimized feedback.
Several parameter descriptions are too terse. load_template.name ('Template name (uses first match if multiple exist)'), load_template.template_id ('Unique template identifier (preferred)'), and get_schema_help.section_path ('Optional path to specific section') lack depth on format, constraints, or examples of valid paths. Descriptions under 50 chars for complex parameters reduce LLM clarity.
Error recovery guidance is minimal. Tools do not clearly indicate which errors are retryable, user-fixable, or fatal. For example, simulate_des and validate_model can fail with schema validation errors but do not return suggested fixes or next steps like 'Call get_schema_help() to see valid formats.' This violates the recovery-guide pattern.
list_templates and load_template parameter descriptions do not clarify mutual exclusivity or usage patterns. For example, list_templates accepts multiple filters (schema_type, domain, complexity, tags) but does not explicitly state how they combine (AND vs OR), or whether all are optional (they appear to be). Undocumented dependencies cause misuse.
Pagination support is absent. list_templates returns 'available templates' but does not clarify result count limits, pagination tokens, or total counts. Tools accepting filters (list_templates.tags) without pagination risk returning hundreds of results and blowing context windows. Pattern recommends paginated-result with offset/limit and total.
No idempotency guarantees stated. save_model with overwrite=true could lead to unintended state loss if LLMs retry on ambiguous failures. No mention of idempotent behavior or confirmation patterns for destructive operations. Pattern guidance recommends confirming before irreversible changes.
Parameter naming could be clearer in some cases. validate_model.validation_mode uses a generic name with opaque values ('partial', 'strict', 'structure'). Better names like 'schema_validation_level' or 'validation_strictness' would clarify intent without reading descriptions.