algotest-backtester
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ALGO_PROFILE | No | Path to the persistent login profile directory for AlgoTest. | /root/algotest-mcp/profile |
| CHROMIUM_PATH | No | Path to the Chromium executable. | /usr/bin/chromium |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| backtest_strategyA | Accept a natural-language strategy request, configure AlgoTest Backtester, and either return a preview or run it when confirm=true. Never performs live trading. |
| preview_backtestB | Configure AlgoTest Backtester in the local browser profile without starting a backtest. Use this first. |
| run_backtestB | Configure and run AlgoTest Backtester. Requires confirm=true because it consumes a backtest quota. Never use for live trading. |
| get_resultsA | Read the currently visible AlgoTest Backtest result metrics without starting a new run. |
| close_browserA | Close the local automation browser while preserving the persistent login profile. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
backtest_strategy overlaps heavily with both preview_backtest and run_backtest, since it can either preview or run a strategy depending on confirm. This makes it unclear when an agent should use backtest_strategy versus the more specific preview/run tools.
All five tool names follow a consistent snake_case verb_noun pattern: backtest_strategy, preview_backtest, run_backtest, get_results, close_browser. This is predictable and easy to scan.
Five tools is well-scoped for a browser-automation backtesting workflow. Each tool maps to a meaningful step in the process without unnecessary bloat.
The set covers the core workflow: preview, run, retrieve results, and clean up. Minor gaps exist, such as no explicit cancel or historical results retrieval, but agents can likely complete the main backtest lifecycle.