MCP server for ITASCA 3DEC discrete element simulation control and documentation. Provides tools for browsing/searching 3DEC documentation and for executing simulation tasks and managing runs through a threedec-mcp-bridge WebSocket service running inside 3DEC GUI.
Server has 12 tools with consistent naming (verb_noun pattern: browse_*, query_*, execute_*, check_*, list_*, interrupt_*) and descriptions present for all. However, parameter descriptions are minimal or absent in several tools. Input schemas are visible and properly typed, but output schemas are not documented. Error handling guidance is missing. Documentation tools (browse_*, query_*) are well-structured with pagination; execution tools (execute_task, execute_code) lack timeout validation and error recovery guidance. No tool annotations (readOnlyHint/destructiveHint) despite clear risk classifications.
Browse 3DEC command documentation with filtering and pagination
Browse 3DEC FISH scripting language documentation with filtering and pagination
Browse 3DEC Python API documentation with filtering and pagination
Browse 3DEC reference documentation index
Check the status of a running or completed task in the 3DEC simulation
Execute Python code directly in the 3DEC embedded Python environment via the WebSocket bridge
Execute a Python script or 3DEC command task in the 3DEC simulation environment via the WebSocket bridge
Interrupt or cancel a running task in the 3DEC simulation
Output schemas not documented. Tools return results but LLMs cannot infer response structure (fields, types, pagination). Forces agents to guess what data is available.
No tool annotations (readOnlyHint, destructiveHint, idempotentHint). Tools are marked with Risk classifications (READ_ONLY, WRITE, REVERSIBLE) but not exposed to MCP clients via annotations. Agents cannot determine safety without reading descriptions.
Execution tools (execute_task, execute_code) lack error recovery guidance. No documentation of what happens on timeout, WebSocket failure, or invalid code. Agents cannot self-correct.
Inferred effective spec: <=2025-11-25.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 46 | <=2025-11-25 | v2 |
List all tasks currently running or completed in the 3DEC simulation
Search 3DEC command documentation using BM25 full-text search
Search 3DEC FISH scripting language documentation using BM25 full-text search
Search 3DEC Python API documentation using BM25 full-text search
Parameter descriptions are minimal. 'code' param in execute_task/execute_code lacks format guidance (Python vs 3DEC syntax?). 'timeout_ms' lacks range constraints (min/max). LLMs cannot validate inputs.
No confirmation/dry-run pattern for destructive operations. execute_task and execute_code can modify simulation state but offer no preview or confirmation step. Agents may execute unintended code.