No user-submitted related servers found.
Scored across 64 tools
Tools are mostly distinct, with clear read/create/update/delete boundaries per resource domain. Minor overlap exists between list_projects and read_project (both can list projects), and stop_live_algorithm vs liquidate_live_algorithm could be misselected by an agent not reading carefully.
Most tools follow a consistent verb_noun snake_case pattern (create_backtest, read_backtest, list_backtests, delete_file). Deviations include object vs object_store prefixes, read_object_store_file_job_id which actually creates a job, and read_lean_versions used for listing.
This server exposes 64 tools, well above the 25+ threshold the rubric flags as too many for typical agent use. Even though the broad platform has genuine sub-domains, the sheer number makes the set heavy to navigate and increases the chance of misselection.
The tool set covers most core lifecycle workflows: projects, files, compiles, backtests, live algorithms, optimizations, object store, and collaboration. A few minor gaps exist, such as no ability to update optimization parameters after creation, no backtest abort, and no live algorithm update, but these are workable.
