No user-submitted related servers found.
Scored across 30 tools
The toolset separates phases clearly (inspect/register/preview, draft/validate/change, prepare/start/run), and most tools have unique resource-action pairings. Minor confusion exists between register_dataset and register_local_dataset, and between inspect_dataset and preview_dataset, since both deal with bounded CSV/dataset inspection.
Almost every tool follows a consistent verb_noun snake_case pattern (register_dataset, preview_dataset, start_strategy_run, get_run_logs). The single outlier 'doctor' breaks the pattern, and 'list_jobs' is slightly less descriptive than the strategy-specific names, but the convention is otherwise uniform.
30 tools is above the 25+ threshold and feels heavy for a typical MCP server, even though the lifecycle is broad. The set could be consolidated into fewer, higher-level tools or grouped behind subresources.
The server covers the full dataset/strategy/run lifecycle: ingest and derive datasets, create/validate/deploy strategy drafts, execute and compare runs, and render reports. Notable gaps are lack of dataset enumeration/listing and no explicit discard/delete operation for strategy drafts, though immutability and approval flows mitigate this.