No user-submitted related servers found.
Scored across 38 tools
Each tool targets a distinct action or resource, from order management to session health and scenario controls. No two tools have overlapping purposes; even similar actions like cancel_algo and cancel_replace are clearly different (algo vs. single order).
All tool names follow a consistent verb_noun pattern in snake_case, e.g., advance_time, approve_action, check_algo_status, diff_snapshot, fix_session_issue. The naming is predictable and easy to understand.
38 tools is significantly above the typical 3-15 range for a well-scoped MCP server. While the domain of trading simulation is complex, the count feels excessive and may overwhelm an agent, reducing coherence.
The tool surface covers the core workflows: order lifecycle (send, cancel, replace, modify), algo orders, session management, scenario simulation, logging, and validation. Minor gaps exist (e.g., no direct market data subscription tool), but most essential operations are present.