# io.github.Schoasch/backtesting-arena (remote · tradingstrategies.work) Crypto backtesting & Bitcoin cycle analytics. Point-in-time, DSR-corrected, look-ahead-aware. - Trust score: 78/100 (medium) - Change this week: +10 - Registry status: active - Liveness: live - Owner verified: no - Last scored: 2026-08-03 ## Components - remote · `tradingstrategies.work`: 78/100 (this document), [markdown](https://verifymcp.io/servers/schoasch-backtesting-arena/api-mcp.md), [page](https://verifymcp.io/servers/schoasch-backtesting-arena/api-mcp) ## Channel facts - Endpoint: `https://tradingstrategies.work/api/mcp` - Transports: `streamable-http` - Auth: `none` - Version: `1.2.0` ## Trust breakdown How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog) Scored 2026-08-03. - **Endpoint Security**: 94/100 - The endpoint's TLS certificate is valid, in date, and uses a strong key. - Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token. - HTTPS is enforced; there's no plaintext access path. - The HSTS (Strict-Transport-Security) header is present. - DNSSEC check failed: this domain isn't protected by DNSSEC. - The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. - **Transport & Reachability**: 100/100 - Verified streamable-http transport via a live MCP handshake. - **Schema Quality & AI Usability**: 58/100 - AI-judged instruction clarity (excellent). - Context-footprint check failed: tool/resource definitions use about 23363 tokens (~315/item across 74 items; 74 tools + 0 resources), over budget; trim descriptions and params. - Usage-examples check failed: none of the tools include examples. - **Stability & Change Management**: 27/100 - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses. - **Tool Coverage**: 100/100 - 100% of tools have a non-trivial description (not blank, and not just the tool's name). - 100% of tool parameters carry a description. - **Capabilities**: 100/100 - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28. ## Install ### Claude ```bash claude mcp add --transport http schoasch-backtesting-arena https://tradingstrategies.work/api/mcp ``` ### Codex ```toml [mcp_servers.schoasch-backtesting-arena] url = "https://tradingstrategies.work/api/mcp" ``` ### opencode ```json { "$schema": "https://opencode.ai/config.json", "mcp": { "schoasch-backtesting-arena": { "type": "remote", "url": "https://tradingstrategies.work/api/mcp", "enabled": true } } } ``` ### OpenClaw ```bash openclaw mcp add schoasch-backtesting-arena --url https://tradingstrategies.work/api/mcp --transport streamable-http ``` ### Hermes ```yaml mcp_servers: schoasch-backtesting-arena: url: "https://tradingstrategies.work/api/mcp" ``` ### Other ```json { "mcpServers": { "schoasch-backtesting-arena": { "type": "http", "url": "https://tradingstrategies.work/api/mcp" } } } ``` The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs. ## Changelog Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims. ### 2026-08-02 (score 78, +1) No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes. ### 2026-08-01 (score 77, −1) - [security] Tool “arena_get_volatility_history” rewrote its description, which is the text the model reads - [security] Tool “arena_run_universe_backtest” rewrote its description, which is the text the model reads - [security] Tool “arena_get_max_pain” rewrote its description, which is the text the model reads - [cosmetic] “arena_get_strategy_insights” reworded the description of “interval” - [cosmetic] “arena_get_strategy_performance_by_regime” reworded the description of “interval” - [cosmetic] “arena_get_volatility_history” reworded the description of “fields” - [cosmetic] “arena_list_backtests” reworded the description of “interval” - [cosmetic] “arena_run_universe_backtest” reworded the description of “pairs” - [cosmetic] “arena_run_universe_backtest” reworded the description of “universe_id” - [cosmetic] “arena_get_signal_status” reworded the description of “interval” - [cosmetic] “arena_get_strategy_filter_effect” reworded the description of “interval” - [cosmetic] “arena_get_strategy_performance” reworded the description of “interval” ### 2026-07-31 (score 78, +6) - [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server ### 2026-07-30 (score 72, +3) - [functional] Schema quality: good → excellent ### 2026-07-28 (score 69, +1) - [functional regression] Schema quality: 229 → 272 - [functional improvement] Tool coverage: 78% → 100% ### 2026-07-27 (score 68, +1) - [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server ### 2026-07-26 (score 67) First indexed and scored. ## MCP tools (74) ### `arena_get_pulse` (~232 tokens) Get Arena Pulse Today Daily 0-100 heat score for the Bitcoin market, aggregated from 8 components (BTC-Cycle, F&G, Altcoin-Season, Bullmarket-Ampel, Funding-Rate, Hash-Ribbons, Mayer-Multiple, MVRV-Z). Returns score, band label, color, 7d/30d delta, verdict, components breakdown, plus score_percentile ranking today’s score against its own history (e.g. 42 = 44th percentile — how hot/cold vs history, not just the raw number). [Free tier] Input parameters: - `context` (string, required): Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVE… ### `arena_get_cycle` (~469 tokens) Get Crypto Cycle Snapshot (BTC / ETH / SOL) Crypto cycle position — where are we in the cycle? Default BTC: point-in-time 10-indicator aggregation (MVRV-Z, NUPL, Puell, Pi-Cycle, Funding, Hash-Ribbons, Power-Law, Rainbow, F&G, Mayer). Pass asset=ETH or asset=SOL for a per-coin cycle read built from the transferable price-derived indicators (Mayer, weekly-RSI, 200-week-MA distance) with renormalized weights; BTC-native indicators (halving, dominance, mining, hash-ribbons, F&G, Pi-Cycle, on-chain) are explicitly returned as `not_applicable` rather than faked. All return raw + Z-Score, signal enum, and a `percentiles` block ranking each indicator against that asset’s own history. BTC additionally returns `highlights[]` (rule-based markers for currently unusual indicator values — descriptive, versioned ruleset, no direction or advice; empty array = nothing unusual) and `price_context` (price at scoring time vs live spot with drift % — the scores are based on the scoring-time price, not the live spot). Point-in-time scored — not reconstructable from a generic price API. Note for volatility questions: this tool carries the regime context around a volatility reading (Funding, Mayer, Pi-Cycle) but not the volatility series itself — that is arena_get_volatility_history. Related: arena_get_historical_analog (what followed states like this one), arena_get_bullmarket_ampel, arena_get_pulse. [Free tier] Input parameters: - `asset` (string): Which asset’s cycle. Default BTC. ETH/SOL return a price-derived cycle read with not_applicable fields for BTC-native indicators. - `context` (string, required): Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVE… ### `arena_get_spot_price` (~203 tokens) Get BTC/ETH/SOL Spot Price Current BTC, ETH and SOL spot price — what is Bitcoin (or ETH/SOL) worth right now? Live USDT-quoted last price plus 24h change %, high and low from Binance. Use this to anchor the connector’s own analytics (cycle, historical-analog, gem scores) with the current market price instead of switching to web search mid-analysis. Context only — not a recommendation. [Free tier] Input parameters: - `context` (string, required): Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVE… ### `arena_get_stablecoin_supply` (~223 tokens) Get Stablecoin Supply Trend Aggregate stablecoin supply (crypto-liquidity proxy) — is the liquidity impulse turning or accelerating? macro_regime only gives the 30d delta; this exposes the trend: current supply, 30d/90d change (USD + %), and acceleration (last-30d vs prior-30d change) plus a compact time series so direction and speed are visible, not just a single delta. Source DefiLlama peggedUSD. Descriptive only, not a signal. [Free tier] Input parameters: - `context` (string, required): Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVE… ### `arena_get_etf_flows` (~278 tokens) Get Spot-ETF Net-Flow Trend (BTC / ETH / SOL) Spot-ETF net flows (USD millions) — is the flow impulse turning or accelerating? The summary only gives point-in-time deltas; this exposes the trend: 30d/90d net flow, acceleration (last-30d vs prior-30d net flow), a direction label (inflows/outflows/flat) and a compact cumulative-inflow time series so direction and speed are visible, not just a single delta. Default BTC; pass asset=ETH or asset=SOL. Source SoSoValue. Descriptive only, not a signal. [Free tier] Input parameters: - `asset` (string): Which spot-ETF flows. Default BTC. - `context` (string, required): Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVE… - `days` (integer): Length of the returned cumulative series in days. Default 365, clamped 90–1095. ### `arena_get_altcoin_season` (~189 tokens) Get Altcoin Season Snapshot Daily Altcoin-Season indicator (v7 Native-Filter methodology). Returns BTC-Dominance, Alt-Dominance, 4 Layer-1 signals (USDT.D, USDC.D, BTC-DOM, ETH-DOM), overall color (red/amber/green) + Top-50 CoinGecko snapshot. [Free tier] Input parameters: - `context` (string, required): Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVE… ### `arena_get_fear_greed` (~173 tokens) Get Fear & Greed Index Crypto Fear & Greed Index from alternative.me with historical context. Returns current value 0-100, classification (extreme fear/fear/neutral/greed/extreme greed), recent history, plus arena-specific cadence cache for change-detection. [Free tier] Input parameters: - `context` (string, required): Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVE… ### `arena_get_bullmarket_ampel` (~158 tokens) Get Bullmarket Ampel Snapshot Bitcoin Bullmarket-Ampel current state (0-5 active stages). Returns active_count, stage_history, stage breakdown. Higher count = more bull-market signals firing. [Free tier] Input parameters: - `context` (string, required): Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVE… ### `arena_get_funding_rate` (~168 tokens) Get Funding Rate Snapshot Latest aggregate Binance Perpetual Funding Rate (8h cadence). Returns value, 30d moving average and Z-Score. Positive = longs pay shorts (bullish bias), negative = shorts pay longs (bearish bias). [Free tier] Input parameters: - `context` (string, required): Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVE… ### `arena_get_hash_ribbons` (~165 tokens) Get Hash Ribbons Snapshot Latest Hash Ribbons indicator (Charles Edwards). Returns 30d and 60d hashrate moving averages — when 30d > 60d after a capitulation, signals miner recovery (bullish). [Free tier] Input parameters: - `context` (string, required): Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVE… ### `arena_get_mayer_multiple` (~231 tokens) Get Mayer Multiple Returns the current Mayer Multiple — BTC price divided by its 200-day SMA — with the underlying price and SMA. Trace Mayer (2014) bands: <0.7 capitulation, 0.7–1.5 neutral, 1.5–2.4 bullish, >2.4 euphoria. One ratio, not a regime call: for the multi-indicator cycle read use arena_get_cycle, for the series behind this number arena_get_mayer_multiple_history. The bands are historical description, not thresholds to trade. [Free tier] Input parameters: - `context` (string, required): Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVE… ### `arena_get_macro_regime` (~428 tokens) Get Macro Regime Snapshot Daily Macro Regime snapshot from 18 components in 6 tiers (Liquidity 30%, Financial Conditions 20%, Risk Appetite 15%, Crypto Liquidity 10%, Business Cycle 15%, Inflation/Real Rates 10%). FRED-sourced. Returns composite_score (0-100), regime_label (risk_off/neutral/risk_on_leaning/risk_on), cycle_phase_label (contraction/early_expansion/mid_expansion/late_expansion), matrix_quadrant (sweet_spot/late_cycle_warning/crisis/recovery), tier_scores (6 sub-scores), components (flat key/value of all 18), plus stale_components_detail dating each stale input (last_good_date + age_days + discontinued flag for series the upstream has retired for good) so freshness is quantified, not a vague caveat. Two component keys mean something narrower than their name suggests, so read them carefully: `vix_score` is the derived 0-100 score (a value of 71 means VIX around 18.6), NOT the VIX index level — the raw Cboe level is not redistributed over this channel; and `broad_dollar_index` is FRED DTWEXBGS (Broad USD Index, Jan 2006 = 100), NOT the ICE DXY, so readings near 120 are normal. The former names `vix` and `dxy` are still present with identical values but are deprecated and listed in deprecated_fields with their removal date. [Free tier] Input parameters: - `context` (string, required): Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVE… ### `arena_get_btc_macro_correlations` (~260 tokens) Get BTC × Macro Correlations Pre-aggregated weekly correlations between Bitcoin and 13 macro components (Fed Net Liquidity, VIX, DXY, Real Yield 10Y, NFCI, HY Credit Spread, Yield Curve, etc.) + 4 asset classes (Gold, SPX, Nasdaq, DXY). Returns quadrant_performance (BTC return stats per 2D-matrix quadrant — annualized return, vol, max drawdown, positive-period%), component_correlations (Pearson 90d/1y/5y per macro component + quartile-performance), asset_correlations (Pearson per window + per quadrant), current_quadrant. Historical analysis only — not investment advice. [Free tier] Input parameters: - `context` (string, required): Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVE… ### `arena_get_btc_market_structure` (~273 tokens) Get BTC Market Structure Daily Bitcoin market structure from 1000-bar Phantomflow adaptation (BTCUSDT 1d). Returns current_trend (up/down/sideways), last trend change timestamp, counts of waves + fractals, last-5 fractals on each side (up = pivot highs, down = pivot lows), and trend_context: previous trend + its duration, flip_age_days, and a descriptive historical flip base rate over the SAME 1000 bars (total flips, share reverted within 5 bars, median trend duration) — a fresh same-day flip is the least reliable observation, the base rate says how often such flips reverted historically; it is NOT a forecast for the current flip. Educational analysis of price action — no signal, no recommendation. [Free tier] Input parameters: - `context` (string, required): Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVE… ### `arena_get_key_levels` (~235 tokens) Get BTC Key Levels (S/R clusters) Reproducible Bitcoin support/resistance zones — where do past swing pivots cluster? Aggregates the market-structure swing fractals (pivot highs + lows) into price zones within a tolerance band, each with a touch-count (how often the zone was tested), band, last-touch date and signed distance from the current price. Resistance = zones above spot, support = below, nearest-first. Replaces eyeballing levels off a fractal chart with a mechanical clustering. Descriptive only — NOT a prediction of where price turns and NOT a buy/sell signal. [Free tier] Input parameters: - `context` (string, required): Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVE… ### `arena_get_iv_snapshot` (~223 tokens) Get Deribit IV Snapshot Latest Deribit volatility snapshot for BTC or ETH. Returns DVOL (30d vol index), constant-maturity ATM implied vol (30/60/90/180d via options chain), 30d realized vol, and vol risk premium (IV - RV). Useful for position sizing, options strategies, and market regime assessment. Backfill: BTC from 2021-04-01, ETH from 2022-02-15. [Free tier] Input parameters: - `context` (string, required): Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVE… - `currency` (string, required): Currency to fetch IV snapshot for ### `arena_get_pulse_history` (~228 tokens) Get Arena Pulse Historical Series Returns the Arena-Pulse TIME SERIES: one row per day with date, 0–100 score and band, in ascending date order. Use it for trend, turning points and "how did we get here"; for today's value alone call arena_get_pulse (cheaper, one row). Range capped by tier. [Free 30d / Pro 365d / Power unlimited] Input parameters: - `context` (string, required): Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVE… - `days` (integer): Number of days back from today (auto-clamped by tier — Free=30, Pro=365, Power=3650). ### `arena_get_cycle_history` (~253 tokens) Get BTC-Cycle Historical Series Returns the BTC-Cycle TIME SERIES: one row per day with adj_score and z_adj_score, ascending by date. The scores are point-in-time — each day carries the value computed from data available on that day, so the series can be used for look-ahead-free analysis. For the current cycle reading alone call arena_get_cycle; for what similar historical readings were followed by, call arena_get_historical_analog. Range capped by tier. [Free 30d / Pro 365d / Power unlimited] Input parameters: - `context` (string, required): Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVE… - `days` (integer): Number of days back from today (auto-clamped by tier — Free=30, Pro=365, Power=3650). ### `arena_get_altcoin_season_history` (~233 tokens) Get Altcoin-Season Historical Series Returns the Altcoin-Season TIME SERIES: one row per day with overall_color, BTC / alt / stablecoin dominance and BTC price, ascending by date. Use it to see whether capital has been rotating into or out of alts over time; for today's state alone call arena_get_altcoin_season. Range capped by tier. [Free 30d / Pro 365d / Power unlimited] Input parameters: - `context` (string, required): Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVE… - `days` (integer): Number of days back from today (auto-clamped by tier — Free=30, Pro=365, Power=3650). ### `arena_get_funding_rate_history` (~235 tokens) Get Funding-Rate Historical Series Returns the funding-rate TIME SERIES for Binance perpetuals, aggregated at the 8h funding cadence, ascending by date. Positive funding means longs pay shorts (crowded long positioning) and vice versa; sustained extremes are a positioning signal, single prints are noise. For the latest funding value alone call arena_get_funding_rate. Range capped by tier. [Free 30d / Pro 365d / Power unlimited] Input parameters: - `context` (string, required): Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVE… - `days` (integer): Number of days back from today (auto-clamped by tier — Free=30, Pro=365, Power=3650). ### `arena_get_mayer_multiple_history` (~244 tokens) Get Mayer-Multiple Historical Series Returns the Mayer-Multiple TIME SERIES (BTC price ÷ its 200-day SMA), one row per day, ascending by date. Values around 1 mean price sits at its 200d average; historically high readings clustered near cycle tops and low ones near bottoms — a descriptive ratio, not a trigger. For the current value alone call arena_get_mayer_multiple. Range capped by tier. [Free 30d / Pro 365d / Power unlimited] Input parameters: - `context` (string, required): Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVE… - `days` (integer): Number of days back from today (auto-clamped by tier — Free=30, Pro=365, Power=3650). ### `arena_list_onchain_series` (~191 tokens) List Available BRK On-Chain Series Lists all available Bitcoin Research Kit (BRK) on-chain series (21 metrics like MVRV, NUPL, SOPR, Realized-Price, Mayer, Puell, STH/LTH SOPR, Hash-Ribbons). Returns id + label + group. Use the id with arena_get_onchain_latest / _history. [Free tier] Input parameters: - `context` (string, required): Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVE… ### `arena_get_onchain_latest` (~250 tokens) Get On-Chain Series Latest Value Returns the most recent value of ONE on-chain series from the Bitcoin Research Kit as { series_id, metric_name, date, value }. Cheapest way to answer "what is X right now" (MVRV, SOPR, realized price, hash rate, …). Discover valid series_ids with arena_list_onchain_series; for the history behind the number use arena_get_onchain_history. A single reading has no context — pair it with the series percentile before calling any level high or low. [Free tier] Input parameters: - `context` (string, required): Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVE… - `series_id` (string, required): BRK series id, e.g. 'mvrv', 'sopr', 'realized_price'. ### `arena_get_sth_cost_basis` (~205 tokens) Get BTC Short-Term-Holder Cost Basis (latest) Latest BTC short-term-holder cost basis (realized price of coins younger than ~155 days, BRK brk_sth_realized_price) plus derived STH-MVRV (spot ÷ STH cost basis) and an in_loss flag (spot below cost basis = recent buyers underwater in aggregate, historically stress / near local bottoms). Descriptive on-chain context, not a buy/sell signal. [Free tier] Input parameters: - `context` (string, required): Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVE… ### `arena_get_onchain_history` (~265 tokens) Get On-Chain Series Historical Values Returns the full TIME SERIES of one on-chain metric from the Bitcoin Research Kit — date/value pairs in ascending order, with history back to 2009 for most series. Use it for trend and percentile work; for the single current reading call arena_get_onchain_latest, and to discover valid series_ids call arena_list_onchain_series. Values are as-reported: on-chain metrics can be revised retroactively, so this is not a point-in-time vintage. Range capped by tier. [Free 30d / Pro 365d / Power unlimited] Input parameters: - `context` (string, required): Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVE… - `days` (integer): Days back from today (clamped by tier). - `series_id` (string, required): BRK series id, e.g. 'mvrv'. ### `arena_get_max_pain` (~899 tokens) Get Deribit BTC Max Pain (latest + upcoming) Last finalized Deribit BTC options expiry: max_pain_strike, spot_at_expiry, %-diff, put_call_ratio, notional. Plus up to 10 upcoming expiries, each with current live max-pain level, days_to_expiry and open_interest_contracts. On days_to_expiry, mind the clamp: it is floored at 0 and therefore CANNOT tell "expiry is today, still hours away" from "expiry was today, already settled" — the same reading covers a live state and a post-mortem. Use settles_at (full ISO timestamp of the settlement moment) and hours_to_settlement (SIGNED — negative means already settled but not yet finalized, so the row is still listed here) whenever that distinction matters. settlement_time_utc names the settlement time assumed for this market; it is 08:00:00Z for DERIBIT_BTC, measured against the exchange itself (public/get_instruments: 868 of 868 open instruments across 13 expiry dates, daily through quarterly, all exactly 08:00:00 UTC). For a market whose settlement time is not evidenced, all three fields are null rather than guessed — a precise-looking wrong timestamp would be worse than none. Read the OI: a max-pain level is only as meaningful as the open interest behind it — a daily expiry with 2,000 contracts and a quarterly with 154,000 are not the same observation. `oi_available` distinguishes "null" from "not collected". Upcoming expiries also carry open_notional_usd together with notional_spot and notional_spot_date. The two contract fields are the SAME measurement at different observation times, not two different quantities: open_interest_contracts on an upcoming expiry is the open interest at the LATEST daily snapshot, total_contracts on a settled one is the open interest at the LAST snapshot BEFORE expiry (verified in the cron: total_contracts is filled from lastSnap.total_oi_contracts). contracts_as_of names the snapshot those contracts came from. Where it equals expiry_date, contracts and settlement price are same-day — measured on all 64 finalized expiries, so a vintage mix… Input parameters: - `context` (string, required): Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVE… - `market` (string): Options market. Currently only 'DERIBIT_BTC' (default). IBIT planned. ### `arena_get_max_pain_history` (~372 tokens) Get Deribit BTC Max Pain History Historical finalized Deribit BTC options expiries in one call — a complete base rate, not a page. Each row: expiry_date, max_pain_strike, spot_at_expiry, %-diff, P/C ratio, notional, expiry-type flags. With include_open_snapshots=true it also returns the DAILY observation series of still-open expiries, which is what makes the convergence question measurable (does spot drift toward the max-pain level as expiry approaches?). That series starts 2026-05-28, is not backfillable, and its per-expiry depth is thin — check open_snapshot_coverage before computing anything from it. Days auto-capped by tier: Pro 365d, Power 3650d. Related: arena_get_max_pain (current + upcoming), arena_get_iv_snapshot. [API Pro tier] Input parameters: - `context` (string, required): Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVE… - `days` (integer): Days back from today (default 90, capped by tier). - `include_open_snapshots` (boolean): Default false. When true, adds open_snapshots[] (daily observations of not-yet-expired contracts) plus open_snapshot_coverage. Omit for the unchanged response. - `market` (string): Options market. Currently only 'DERIBIT_BTC' (default). ### `arena_get_drift_log` (~192 tokens) Get Data-Quality Drift Log Daily drift log comparing bgeometrics (legacy) vs BRK (canonical-soon) pilot metric pairs. Returns mean / max / outlier counts per pair for the requested window. Used by BRK-migration review (every 4 weeks). [API Pro tier] Input parameters: - `context` (string, required): Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVE… - `days` (integer): Window size in days (default 90, max 365). ### `arena_list_strategies` (~215 tokens) List Available Trading Strategies Lists all backtest strategies (key, label, plan, supported asset classes, primary indicators). Filterable by asset class and plan. Use this before calling arena_run_backtest to discover valid strategy names. [Free tier] Input parameters: - `asset_class` (string): Filter to strategies supporting this asset class (crypto or tokenized_rwa). - `context` (string, required): Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVE… - `lang` (string): Localized names/taglines. Default 'en'. - `plan` (string): Filter to strategies of this plan tier. ### `arena_list_universes` (~159 tokens) List Asset Universes Lists all crypto asset universes (BTC, top-10 crypto, top-50 crypto, etc.) — the underlying pair-sets used by custom-report and universe-backtest endpoints. [Free tier] Input parameters: - `context` (string, required): Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVE… ### `arena_get_universe` (~240 tokens) Get Universe Detail Returns one pair universe in full: its id, label, selection rule and the complete list of pairs it currently contains. Use it to see what you are about to test BEFORE handing a universe_id to arena_run_universe_backtest, or to resolve a universe into explicit pairs. For the list of available universes call arena_list_universes. Universes reflect the CURRENT membership — they are not point-in-time, so a backtest over them carries survivorship bias for the earlier years. [Free tier] Input parameters: - `context` (string, required): Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVE… - `universe_id` (string, required): Universe id, e.g. 'top-10-crypto'. ### `arena_get_strategy_insights` (~398 tokens) Get Strategy Insights Matrix or Detail Aggregated backtest performance per (strategy × interval) cell. If `strategy` AND `interval` provided, returns detail with per-asset breakdown + param variants. Otherwise returns the full matrix (Top-10 cells for Free tier; full for Pro+). [Free Top-10 / Pro+ full] Input parameters: - `asset_type` (string): Restrict to one asset class. - `assets_mode` (string): 'top10' restricts to top-10 pairs by run-count. - `context` (string, required): Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVE… - `interval` (string): Detail mode: interval. Candle interval: '1d' daily, '2d'/'3d' multi-day, '1w' weekly, '1M' monthly. Multi-day candles (2d/3d) are anchored to the Unix epoch, so one of n possible alignments is used.… - `min_runs` (integer): Matrix mode: minimum runs per cell. Default 5. - `ref_strategy` (string): Benchmark reference. Default 'bh'. - `strategy` (string): Detail mode: strategy key (used together with `interval`). ### `arena_get_filter_insights` (~163 tokens) Get Strategy Filter Insights Lift analysis of entry filters (200WMA, Altcoin-Season, ATR-Volatility, Bullmarket-Stage) per strategy combo — baseline vs filtered CAGR/win-rate/drawdown. [API Pro tier] Input parameters: - `context` (string, required): Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVE… ### `arena_get_volatility_insights` (~279 tokens) Get Volatility Insights Breaks realized strategy performance down by VOLATILITY PHASE (low / normal / high) per asset and timeframe, so you can see whether an edge only exists in one volatility regime. Answers "when does this work", not "does this work" — for the overall verdict use arena_get_strategy_insights, for the macro-regime cut arena_get_strategy_performance_by_regime, and for the raw volatility time series arena_get_volatility_history. Cells below min_trades are suppressed rather than shown as noise. [API Pro tier] Input parameters: - `asset_type` (string): Filter by asset class, e.g. 'crypto'. Omit for all. - `context` (string, required): Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVE… - `min_trades` (integer): Minimum trades a cell needs to be reported. Default 20 — lowering it buys coverage with noise. ### `arena_get_sentiment` (~289 tokens) Get Sentiment Dashboard PLATFORM ACTIVITY, NOT MARKET SENTIMENT — despite the name, this reports what is being backtested on Backtesting Arena, not how the market feels. Returns hotAssets, hotStrategies, trendingUp/trendingDown, profitTrend (share of profitable runs per pair), dailyActivity, assetDistribution, strategyAssetMatrix, weeklyTrend and totalRuns over a 7d/30d/90d window. Honesty note: the counts include our own bulk and admin snapshot runs, so this is coverage-weighted attention, NOT a clean crowd signal — never present it as 'traders are bullish on X'. For actual market sentiment use arena_get_fear_greed, arena_get_funding_rate, arena_get_altcoin_season or arena_get_pulse. [Free tier] Input parameters: - `context` (string, required): Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVE… - `period` (string): Aggregation window. Default '7d'. ### `arena_get_strategy_performance` (~432 tokens) Get Strategy Performance Snapshot (per Asset) Aggregated backtest performance for ONE specific (strategy, asset, interval) combination. Returns run_count, avg_cagr, avg_win_rate, avg_drawdown, effective_years, and vs_buy_hold comparison (beats_buy_hold, cagr_delta). For multi-strategy overview use arena_get_strategy_insights. Use this to answer 'How does strategy X perform on asset Y?'. [Free tier] Input parameters: - `asset` (string, required): Crypto pair / symbol (e.g. BTCUSDT, ETHUSDT). Case-insensitive. - `asset_type` (string): Optional asset class filter to disambiguate (e.g. when same pair-name exists in two classes). - `context` (string, required): Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVE… - `interval` (string): Default '1w'. Candle interval: '1d' daily, '2d'/'3d' multi-day, '1w' weekly, '1M' monthly. Multi-day candles (2d/3d) are anchored to the Unix epoch, so one of n possible alignments is used. Measured… - `ref_strategy` (string): Benchmark reference. Default 'bh' (Buy & Hold). - `strategy` (string, required): Strategy key (e.g. rsi_sma, golden_cross). See arena_get_strategies for valid keys. ### `arena_get_strategy_filter_effect` (~396 tokens) Get Strategy Filter Effect Snapshot (per Asset) Per-(strategy, asset, interval) filter-effect analysis. Returns baseline-stats (no filters) + each observed filter-variant's stats with cagr_delta / drawdown_delta / win_rate_delta vs the time-overlap-matched baseline + best_by_cagr pick + not_applicable_filters list (e.g. altcoin_season excluded on BTC-pair). Based on REAL backtest aggregations — not theoretical 2^5 permutations. Use this to answer 'Which filters would improve my backtest for X on Y?'. [Free tier] Input parameters: - `asset` (string, required): Pair / symbol (e.g. BTCUSDT). Case-insensitive. - `context` (string, required): Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVE… - `interval` (string): Default '1w'. Candle interval: '1d' daily, '2d'/'3d' multi-day, '1w' weekly, '1M' monthly. Multi-day candles (2d/3d) are anchored to the Unix epoch, so one of n possible alignments is used. Measured… - `strategy` (string, required): Strategy key (see arena_get_strategies). ### `arena_get_strategy_performance_by_regime` (~430 tokens) Get Regime-Aware Strategy Performance Historical backtest performance for ONE (strategy, asset, interval) combination SPLIT BY macro market regime (sweet_spot / late_cycle_warning / crisis / recovery — classified at each trade's entry date), PLUS a recommendation for the CURRENT live regime. Answers the killer question 'Should I trade this strategy NOW?'. Each regime bucket returns trades, win_rate, avg_pnl_pct, reward_risk_ratio (per-trade mean/stddev, NOT annualized Sharpe), share_of_time_pct and a rating. [Free tier] Input parameters: - `asset` (string, required): Crypto pair / symbol (e.g. BTCUSDT, ETHUSDT). Case-insensitive. - `asset_type` (string): Optional asset class filter to disambiguate identical pair-names. - `context` (string, required): Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVE… - `interval` (string): Default '1w'. Candle interval: '1d' daily, '2d'/'3d' multi-day, '1w' weekly, '1M' monthly. Multi-day candles (2d/3d) are anchored to the Unix epoch, so one of n possible alignments is used. Measured… - `strategy` (string, required): Strategy key (e.g. rsi_sma, golden_cross). See arena_get_strategies. ### `arena_get_edge_reports` (~286 tokens) Get Edge Library — Filter Effect Reports Platform-wide aggregated analysis: how each Pro+ entry filter (200 WMA, ATR low/high/expansion, Altcoin Season, Bullmarket confirm/strict) affects strategy CAGR — baseline vs. filtered, median across all real backtest runs for a given market. Verdict: helps (Δ>+1pp, ≥30 runs) / neutral / hurts / insufficient_data. Filters evaluated in isolation (no stacking). Also returns baseline_net_cagr / filtered_net_cagr (median CAGR after per-side trading costs; verdict/delta stay gross). [Free tier] Input parameters: - `context` (string, required): Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVE… - `market` (string, required): Market to analyze (crypto or tokenized). - `strategy` (string): Restrict to a single strategy key (e.g. golden_cross). Omit for all strategies. - `verdict` (string): Filter by verdict. Default 'all'. ### `arena_get_winners` (~295 tokens) Get Winners List (Top 100 CAGR) Public leaderboard: the highest-CAGR backtest results across all users, with anonymized usernames, pair, strategy, interval and period. Answers "what has scored best on this platform so far". Read it as a selected extreme, not as a recommendation — a top-of-leaderboard entry is the winner of a large search and its edge is upward-biased; arena_get_robustness_field or validate_strategy tell you whether a given result holds up. For the user's own runs use arena_list_backtests. [Free tier] Input parameters: - `asset_class` (string): Asset class filter. Default 'crypto' (D14-separated leaderboard). - `context` (string, required): Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVE… - `limit` (integer): How many entries to return, max 100 (default 100). - `strategy` (string): Restrict the leaderboard to one strategy key, e.g. 'rsi_sma'. Omit for all strategies. ### `arena_list_backtests` (~443 tokens) List Your Backtests Lists the backtest runs belonging to the authenticated user — newest first, with id, strategy, pair, interval, date range and headline metrics per run. Use it to find a run_id, then call arena_get_backtest for its detail or arena_get_backtest_trades for the individual trades. Only your OWN runs; for the public cross-user leaderboard use arena_get_winners. Paginated via limit + offset. [API Pro tier] Input parameters: - `asset_type` (string): Filter by asset class, e.g. 'crypto'. Omit for all. - `context` (string, required): Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVE… - `interval` (string): Filter by candle interval; omit for all. Candle interval: '1d' daily, '2d'/'3d' multi-day, '1w' weekly, '1M' monthly. Multi-day candles (2d/3d) are anchored to the Unix epoch, so one of n possible al… - `limit` (integer): Page size, max 100, default 50. - `offset` (integer): Rows to skip for paging; default 0. - `pair` (string): Filter by pair symbol, e.g. BTCUSDT. Omit for all. - `strategy` (string): Filter by strategy key, e.g. 'rsi_sma'. Omit for all. ### `arena_get_backtest` (~232 tokens) Get Backtest Detail Returns the full record of ONE backtest run by id: strategy, pair, interval, date range, parameters, filters and the aggregate metrics (CAGR, total return, win-rate, max drawdown, trade count, Buy & Hold comparison, net-of-fees figures). Only your own runs (admins may read others). Get ids from arena_list_backtests; for the individual trades add arena_get_backtest_trades; to create a new run use arena_run_backtest. [API Pro tier] Input parameters: - `context` (string, required): Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVE… - `id` (string, required): UUID of the backtest run. ### `arena_get_backtest_trades` (~253 tokens) Get Backtest Trades + Equity Curve Returns the individual round-trips of one of your backtest runs: entry and exit date, entry and exit price, per-trade P&L and the running equity after each trade. Use it when the aggregate metrics are not enough — to see whether a result rests on a handful of outlier trades, how long positions were held, or where the drawdown came from. Needs a run_id from arena_list_backtests; for the aggregates alone use arena_get_backtest. Closed round-trips only — a position still open at the end of the period is not counted. [API Pro tier] Input parameters: - `context` (string, required): Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVE… - `id` (string, required): UUID of the backtest run. ### `arena_get_shared_backtest` (~214 tokens) Get Public Shared Backtest Fetches a backtest that someone published via a share link, addressed by its share_id — no ownership and no Pro tier required, which is what makes it the right tool when a user pastes a /shared/backtests URL. Returns the same result shape as arena_get_backtest (config plus aggregate metrics). Use arena_get_backtest instead for the user's own runs. [Free tier] Input parameters: - `context` (string, required): Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVE… - `share_id` (string, required): Public share id from /shared/backtests URL. ### `arena_get_signal_status` (~316 tokens) Get Signal Status (Ampel) Current signal-status (green/yellow/red) for a strategy on a pair+interval. Backed by the daily check-signals cron — needs at least one user with an active Ampel on this combination. [Free tier] Input parameters: - `context` (string, required): Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVE… - `interval` (string, required): Candle interval: '1d' daily, '2d'/'3d' multi-day, '1w' weekly, '1M' monthly. Multi-day candles (2d/3d) are anchored to the Unix epoch, so one of n possible alignments is used. Measured on our own cor… - `pair` (string, required): Trading pair / symbol. - `strategy` (string, required): Strategy key, e.g. 'rsi_sma'. ### `validate_strategy` (~450 tokens) Validate a strategy/signal (honest backtest) Backtest a trading strategy honestly — look-ahead-aware validation with Deflated-Sharpe-Ratio / multiple-testing correction (Bailey & López de Prado). Returns an EVIDENCE verdict (insufficient_evidence | anecdote | failed_oos | passed_oos) plus metrics, flags and caveats — NOT a buy/sell recommendation. Call this before acting on a strategy or signal list. Accepts a named catalog strategy (type=rules), a timestamped BUY/SELL signal list (signal_list), or a timestamped trade list (trade_list). Checks: realistic next-bar fills (look-ahead/optimism), net of cost, out-of-sample split, and a hard 30-round-trip sample gate (under 30 is always "anecdote"). Not reproducible via generic backtest tools that ignore overfitting. [API Pro tier] Input parameters: - `context` (string, required): Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVE… - `costs` (object): Trading costs. Default 10 bps (crypto) / 5 bps (else) — a gross-only claim usually shrinks once these apply. - `market` (object, required): Which market the claim is about — prices are re-fetched from here, not taken from you. - `oos` (object): How the claim is tested out-of-sample. Omit for the default split — the out-of-sample part is what separates a finding from a fit. - `strategy` (object, required): The claim being validated — supply exactly one of: a catalog strategy (type=rules), your signals (type=signal_list) or your finished trades (type=trade_list). - `window` (object, required): Period over which the claim is checked. ### `arena_run_backtest` (~641 tokens) Run a New Backtest Run ONE strategy on ONE pair over a date range and get the full result: CAGR, total return, max drawdown, win-rate, trade count, Buy & Hold comparison, net-of-fees figures, and a run_id for later retrieval. Synchronous, typically 3–10s. Use this when the user wants a concrete result for a specific setup. For several strategies side by side use arena_compare_strategies; for many pairs at once use arena_run_universe_backtest; to judge whether an EXISTING result is trustworthy rather than produce a new one, use validate_strategy or arena_get_robustness_field. Filters are optional and only remove entries; run once without them for the baseline. A backtest is evidence about the past, never a forecast or a recommendation. Per-day quota: Pro=50, Power=500. [API Pro tier] Input parameters: - `asset_type` (string, required): Asset class. Use 'crypto' unless you are explicitly backtesting a tokenized real-world asset. - `capital` (number): Starting capital in quote currency. Default 10000. Affects absolute figures only, not CAGR or win-rate. - `context` (string, required): Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVE… - `date_from` (string, required): Start date, YYYY-MM-DD. Earlier than the pair listing is clamped to the first available candle. - `date_to` (string): End date, YYYY-MM-DD. Default: today. - `filters` (object): Optional entry filters (Pro+). Each one only ever REMOVES entries — filters never create trades. Omit for the unfiltered baseline. - `interval` (string, required): Candle interval: '1d' daily, '2d'/'3d' multi-day, '1w' weekly, '1M' monthly. Multi-day candles (2d/3d) are anchored to the Unix epoch, so one of n possible alignments is used. Measured on our own cor… - `pair` (string, required): Crypto pair symbol, e.g. BTCUSDT, ETHUSDT, SOLUSDT. - `params` (object): Strategy-specific parameters, e.g. { rsi_period: 14 }. Omit to use the audited defaults — changing them without a reason is how overfitting starts. - `strategy` (string, required): Strategy key — use arena_list_strategies to find valid keys. ### `arena_compare_strategies` (~582 tokens) Compare 2-5 Strategies Run 2–5 strategies against the SAME pair, interval and date range and return per-strategy metrics plus a comparison summary (best by CAGR, best by win-rate, worst by drawdown). Use this when the user asks which of several strategies fits a market — it holds every variable but the strategy fixed, which a series of separate arena_run_backtest calls does not guarantee. For one strategy across many pairs use arena_run_universe_backtest instead. Caveat worth passing on: comparing N strategies and reporting the winner IS multiple testing — the winner’s edge is upward-biased. arena_get_robustness_field puts a counted N on that. Sequential, expect 10–50s. Per-day quota: Pro=20, Power=200. [API Pro tier] Input parameters: - `asset_type` (string, required): Asset class. Use 'crypto' unless you are explicitly backtesting a tokenized real-world asset. - `capital` (number): Starting capital in quote currency. Default 10000. Affects absolute figures only, not CAGR or win-rate. - `context` (string, required): Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVE… - `date_from` (string, required): Start date, YYYY-MM-DD. Earlier than the pair listing is clamped to the first available candle. - `date_to` (string): End date, YYYY-MM-DD. Default: today. - `filters` (object): Optional entry filters (Pro+). Each one only ever REMOVES entries — filters never create trades. Omit for the unfiltered baseline. - `interval` (string, required): Candle interval: '1d' daily, '2d'/'3d' multi-day, '1w' weekly, '1M' monthly. Multi-day candles (2d/3d) are anchored to the Unix epoch, so one of n possible alignments is used. Measured on our own cor… - `pair` (string, required): Crypto pair symbol, e.g. BTCUSDT — the same pair for every strategy. - `strategies` (array, required): The 2–5 strategies to compare, each with optional own params. ### `arena_run_universe_backtest` (~839 tokens) Run Backtest on a Pair Universe (async) Backtests one strategy across a whole pair universe. Pair cap depends on your API tier: Pro 50, Power 250 — Power therefore covers crypto-top-250 in ONE job instead of five, which matters because five jobs mean five separate result sets you have to merge by hand, and merging across different pair sets is exactly how a ranking ends up measuring pair selection instead of strategy quality. THIS CALL IS ASYNCHRONOUS AND RETURNS NOTHING BUT A job_id: the result is NOT in this response. You MUST poll arena_get_job_status until status is 'completed'. Budget the wait — background runtime is roughly 1.5 s per pair, so 50 pairs ≈ 1–2 min and a 250-pair job ≈ 6 min; estimated_seconds in the create-response gives the current estimate. Provide either universe_id (call arena_list_universes) OR explicit pairs[]. Benchmarks bnh_fixed and dca_reference are accepted here — run one of them over the SAME universe and interval before reading any result, because an excess over buy-and-hold is not a statement without the buy-and-hold value itself: measured on 41 common pairs, bnh_fixed sits at +0.2 % while the naive figure suggested −22 %, and a strategy 'beating' a −54 % benchmark means 'do not own this asset', not 'this strategy is good'. NOTE ON PERSISTENCE: universe results live ONLY in the job response (api_jobs.result). They are deliberately not written to backtest_runs, so they carry no filter_binding and no coin-denominated history, and you will not find them later via arena_list_backtests — copy what you need out of the job result. Per-day quota: Pro=5, Power=50. [API Pro tier] Input parameters: - `capital` (number): Starting capital in quote currency. Default 10000. Affects absolute figures only, not CAGR or win-rate. - `context` (string, required): Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVE… - `date_from` (string, required): Start date, YYYY-MM-DD. Earlier than the pair listing is clamped to the first available candle. - `date_to` (string): End date, YYYY-MM-DD. Default: today. - `filters` (object): Optional entry filters (Pro+). Each one only ever REMOVES entries — filters never create trades. Omit for the unfiltered baseline. - `interval` (string, required): Candle interval: '1d' daily, '2d'/'3d' multi-day, '1w' weekly, '1M' monthly. Multi-day candles (2d/3d) are anchored to the Unix epoch, so one of n possible alignments is used. Measured on our own cor… - `pairs` (array): Explicit pair list. Hard schema limit 250; the effective cap is your tier (Pro 50, Power 250). Use instead of universe_id. - `params` (object): Strategy-specific parameters applied to EVERY pair in the universe. Omit for audited defaults. - `strategy` (string, required): Strategy key — call arena_list_strategies. - `universe_id` (string): Pre-curated universe — call arena_list_universes for valid IDs. Capped by tier (Pro 50, Power 250); a larger universe is rejected rather than silently truncated. ### `arena_get_job_status` (~190 tokens) Get Async Job Status Polls an async job by job_id (created via arena_run_universe_backtest). Returns status (pending/running/completed/failed), progress_pct, pairs_completed, and once completed: the full result (summary + per-pair results). [Free tier] Input parameters: - `context` (string, required): Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVE… - `job_id` (string, required): UUID job_id returned by arena_run_universe_backtest. ### `arena_run_grid_backtest` (~589 tokens) Run a Grid-Trading Backtest Simulate a GRID BOT (buy-low / sell-high ladder inside a fixed price range) on historical candles. Returns final value, return %, CAGR, trade count, fees paid and a Buy & Hold comparison. This is a different machine from the strategy backtester: grid bots earn from oscillation inside a range, not from trend — for signal-based strategies use arena_run_backtest instead. The result depends heavily on the range you choose (low_price / high_price); a range the price left early makes the bot idle, so treat range choice as part of the hypothesis, not a detail. Free tier limited to BTCUSDT/ETHUSDT. Per-day quota: Free=5, Pro=50, Power=500. [Free / Pro / Power tier] Input parameters: - `context` (string, required): Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVE… - `end_date` (string, required): Simulation end, YYYY-MM-DD. - `entry_price` (number): Optional price at which the bot starts; default is the first close in the range. - `fee_rate` (number, required): Per-trade fee fraction, e.g. 0.001 for 0.1% (Binance spot taker). - `grid_count` (integer, required): Number of grid levels between low_price and high_price (2–200). More levels = more, smaller trades = more fees. - `grid_type` (string, required): Level spacing: 'arithmetic' = equal price steps, 'geometric' = equal percentage steps (usually the better fit for crypto). - `high_price` (number, required): Upper bound of the grid range, in quote currency. Above it the bot is fully in cash and stops selling. Must exceed low_price. - `low_price` (number, required): Lower bound of the grid range, in quote currency. Below it the bot is fully invested and stops buying. - `pair` (string, required): Crypto pair symbol, e.g. BTCUSDT. Free tier: BTCUSDT or ETHUSDT only. - `start_date` (string, required): Simulation start, YYYY-MM-DD. - `stop_loss_price` (number): Optional: liquidate the whole grid and stop once price falls to this level. - `take_profit_price` (number): Optional: liquidate the whole grid and stop once price rises to this level. - `total_investment` (number, required): Capital in USDT spread across the grid; min 100. ### `arena_quote_report` (~365 tokens) Quote a Custom Report Get a pricing quote for a custom report (universe-backtest PDF + Excel) without committing to a purchase. Returns price, universe size + preview, excluded pairs, and filter config. Crypto universes use top-N tiers (top-10 … top-250) or a custom pair list. [API Pro tier] Input parameters: - `asset_type` (string): Asset class; currently 'crypto' only (default). - `context` (string, required): Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVE… - `custom_pairs` (array): Explicit pair list — required when universe_tier='custom', ignored otherwise. - `discount_code` (string): Optional retention-discount code. - `interval` (string, required): Candle interval the report is computed on: '1d', '1w' or '1M'. - `period_label` (string, required): History covered by the report. Longer periods cross more market regimes and cost more compute. - `strategy` (string, required): Strategy key (use arena_list_strategies for valid values). - `strategy_params` (object): Strategy parameters applied across the whole universe; omit for audited defaults. - `universe_tier` (required): 'top-10' / 'top-50' / 'top-100' / 'top-250' (crypto) or 'custom' with customPairs[]. ### `arena_get_report_status` (~179 tokens) Get Custom-Report Job Status Poll the status of a Custom-Report job. Lifecycle: pending_payment → queued → running → generating → success/failed. Returns progress_pct, succeeded/failed counts, plus pdf_url / xlsx_url when done. [API Pro tier] Input parameters: - `context` (string, required): Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVE… - `job_id` (string, required): Job UUID returned by checkout. ### `arena_subscribe_signal_alerts` (~408 tokens) Subscribe to Strategy Signal Alerts Fires when an existing Ampel-Config's signal flips (BUY ↔ SELL). Prerequisite: the user must have created that ampel-config in the web UI (`/dashboard/ampel`) — pass its UUID here; this tool cannot create one. Optional signal_types filter narrows to BUY-only or SELL-only. For the current signal state without subscribing, call arena_get_signal_status. Creates a standing subscription; it does not return a value now — collect fired updates with arena_check_subscription_updates (polling) or receive them by webhook, and end it with arena_cancel_subscription. For the CURRENT value instead of a change notification, call the matching read tool. [API Pro tier and up — max 3 active subscriptions for Pro, 20 for Power] Input parameters: - `ampel_config_id` (string, required): UUID einer existierenden ampel_configs-Row im gleichen User-Account. - `context` (string, required): Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVE… - `delivery_method` (string): How updates reach you: 'polling' (default — collect via arena_check_subscription_updates) or 'webhook' (we POST to your URL). - `expires_at` (string): ISO-8601 timestamp after which the subscription auto-deactivates. Omit to keep it active until cancelled. - `signal_types` (array): Optional filter. Default: both BUY and SELL fire. - `webhook_url` (string): HTTPS endpoint we POST to. Required when delivery_method=webhook, ignored otherwise. ### `arena_subscribe_cycle_changes` (~349 tokens) Subscribe to BTC Cycle Band Changes Fires when the BTC-Cycle band changes (capitulation → risk-off → neutral → constructive → euphoric). Optional bands filter restricts to specific target bands. For the current band without subscribing, call arena_get_cycle. Creates a standing subscription; it does not return a value now — collect fired updates with arena_check_subscription_updates (polling) or receive them by webhook, and end it with arena_cancel_subscription. For the CURRENT value instead of a change notification, call the matching read tool. [API Pro tier and up — max 3 active subscriptions for Pro, 20 for Power] Input parameters: - `bands` (array): Filter to bands of interest. Default: any change triggers. - `context` (string, required): Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVE… - `delivery_method` (string): How updates reach you: 'polling' (default — collect via arena_check_subscription_updates) or 'webhook' (we POST to your URL). - `expires_at` (string): ISO-8601 timestamp after which the subscription auto-deactivates. Omit to keep it active until cancelled. - `webhook_url` (string): HTTPS endpoint we POST to. Required when delivery_method=webhook, ignored otherwise. ### `arena_subscribe_pulse_changes` (~366 tokens) Subscribe to Arena-Pulse Score Threshold Crossings Fires when the daily 0–100 Arena-Pulse score crosses threshold_above (upward) or threshold_below (downward). At least one threshold is required. For the current score without subscribing, call arena_get_pulse. Creates a standing subscription; it does not return a value now — collect fired updates with arena_check_subscription_updates (polling) or receive them by webhook, and end it with arena_cancel_subscription. For the CURRENT value instead of a change notification, call the matching read tool. [API Pro tier and up — max 3 active subscriptions for Pro, 20 for Power] Input parameters: - `context` (string, required): Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVE… - `delivery_method` (string): How updates reach you: 'polling' (default — collect via arena_check_subscription_updates) or 'webhook' (we POST to your URL). - `expires_at` (string): ISO-8601 timestamp after which the subscription auto-deactivates. Omit to keep it active until cancelled. - `threshold_above` (number): Fire when score rises across this value. - `threshold_below` (number): Fire when score falls across this value. - `webhook_url` (string): HTTPS endpoint we POST to. Required when delivery_method=webhook, ignored otherwise. ### `arena_subscribe_bullmarket_stage` (~367 tokens) Subscribe to Bullmarket-Ampel Stage Changes Fires when the Bullmarket-Ampel active stage count (0–5) changes. Optional direction filter (up/down/any) plus specific stages of interest. For the current stage count without subscribing, call arena_get_bullmarket_ampel. Creates a standing subscription; it does not return a value now — collect fired updates with arena_check_subscription_updates (polling) or receive them by webhook, and end it with arena_cancel_subscription. For the CURRENT value instead of a change notification, call the matching read tool. [API Pro tier and up — max 3 active subscriptions for Pro, 20 for Power] Input parameters: - `context` (string, required): Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVE… - `delivery_method` (string): How updates reach you: 'polling' (default — collect via arena_check_subscription_updates) or 'webhook' (we POST to your URL). - `direction` (string): Filter to direction. Default 'any'. - `expires_at` (string): ISO-8601 timestamp after which the subscription auto-deactivates. Omit to keep it active until cancelled. - `stages` (array): Specific stages of interest. Default: any change. - `webhook_url` (string): HTTPS endpoint we POST to. Required when delivery_method=webhook, ignored otherwise. ### `arena_list_subscriptions` (~183 tokens) List Active Live-Subscriptions Returns every ACTIVE subscription belonging to the current API key: id, type, trigger configuration, delivery method and expiry. Use it to see what is already running before creating a duplicate, and to get the subscription_id that arena_cancel_subscription needs. Does not return fired updates — that is arena_check_subscription_updates. [API Pro tier] Input parameters: - `context` (string, required): Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVE… ### `arena_check_subscription_updates` (~164 tokens) Check Pending Subscription Updates Returns all undelivered updates for the API key, then marks them as delivered. Call regularly to consume the polling queue. Updates contain payload with subscription_type, current value, previous value, and trigger context. [API Pro tier] Input parameters: - `context` (string, required): Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVE… ### `arena_cancel_subscription` (~203 tokens) Cancel Subscription Deactivates one subscription by id, so it stops firing and frees a slot against the per-tier limit. Returns the deactivated subscription. Idempotent — cancelling an already-cancelled one is a no-op, not an error. Get ids from arena_list_subscriptions. Undelivered updates already queued are not removed. [API Pro tier] Input parameters: - `context` (string, required): Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVE… - `subscription_id` (string, required): Subscription id returned by arena_subscribe_* ### `arena_get_gem_scores` (~236 tokens) Get Altcoin Screener Rankings Altcoin screener ranking — which altcoins look strong right now? Today's CoinGecko Top-200 scored by a composite of 3 factor groups: Mean-Reversion (A), Tokenomics (B), Market-Structure (C). Backtest-validated factors, not a hype list. Limit gated by tier: Free top-10, Pro top-50, Power top-200. [Free tier, daily refresh] Input parameters: - `context` (string, required): Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVE… - `from_rank` (integer): Start from this rank (default 1) - `limit` (integer): Number of coins to return (tier-capped) ### `arena_get_gem_score` (~251 tokens) Get Altcoin Screener Score for One Coin Returns the Altcoin-Screener score for ONE coin, addressed by its CoinGecko id: the composite score, its group breakdown and — for Pro+ — the 9 raw factor values across groups A/B/C. Use it once a candidate is known; to rank or filter the whole screened universe use arena_get_gem_scores (plural), and for how the score behaved out-of-sample use arena_get_gem_validation. The score ranks relative attributes, it is not a price forecast or a buy signal. [Free tier] Input parameters: - `coingecko_id` (string, required): CoinGecko coin ID, e.g. "ethereum", "solana" - `context` (string, required): Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVE… ### `arena_get_gem_validation` (~185 tokens) Get Altcoin Screener Backtest-Lite Validation Bi-weekly equal-weight basket backtest for Top-N screener picks vs BTC and market average. Shows CAGR, max drawdown, win-rate. Free: top-10 default. Pro+: custom N. [Free tier] Input parameters: - `context` (string, required): Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVE… - `top_n` (integer): Basket size (default 10, Pro+ up to 200) ### `arena_get_volatility_history` (~810 tokens) Get BTC Volatility History (RV + ATR%) Daily Bitcoin volatility time series: realized volatility (30d & 90d, √252-annualized, close-to-close) and ATR% (Wilder EMA-14, captures intraday range + gaps), on the same scale. Ranks come in two flavours and they answer different questions — `rvRank`/`atrPctAnnRank` expand from the start of history and are look-ahead-free, but BTC volatility has fallen structurally, so a filter like "rank below 10" mostly picks up that decline rather than a regime; `rvRankRolling`/`atrPctAnnRankRolling` rank against a trailing 2-year window and are the ones to use for cross-epoch regime comparisons. History reaches back to 2009 via a stitched pre-Binance close series; ATR is null before the Binance era because no daily high/low exists that far back (see meta.coverage). Use `from`/`to` for a specific window instead of pulling everything and discarding it, and `granularity`/`fields` to keep long ranges affordable. Agents fetching long ranges should pass `schema_version: "2026-08"` today — it rounds floats and cuts the payload by 30–36 % depending on window length (measured 2026-07-31 on the live series: 36.1 % over 30 days, 35.8 % over 365, 29.8 % over the full 5,508 rows — the saving falls on long ranges because the pre-Binance years carry null ATR, and nulls do not round). It is opt-in until the default flips 2026-11-01. Descriptive — no forecast, no signal. Free tier: last 365 days. Related: arena_get_volatility_phases (current phase per pair), arena_get_iv_snapshot (implied vs. this realized), arena_get_cycle (regime context). [Free tier] Input parameters: - `context` (string, required): Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVE… - `days` (integer): Number of most recent days to return. Free tier capped at 365; API Pro unlimited. Ignored when from/to are given. - `fields` (string): Default full. 'minimal' returns date, close, rv, rvRank, rvRankRolling, atrPctAnnRank, atrPctAnnRankRolling only — measured saving 18–20 % of characters (5,508-row series, 2026-07-31), not a fifth of… - `from` (string): ISO date (YYYY-MM-DD), inclusive. Start of the window. Free tier still only sees the last 365 days. - `granularity` (string): Default daily. weekly/monthly keep the LAST observation of each period (a state, not an average). - `meta` (string): Default full. 'minimal' drops params/params_hash/warmup, which are only useful on the first call. - `schema_version` (string): Default '2026-07' (unchanged output). '2026-08' rounds floats to 2 decimals (ranks 1) and reports the saving. Default flips 2026-11-01. - `to` (string): ISO date (YYYY-MM-DD), inclusive. End of the window. Defaults to the latest bar. ### `arena_get_volatility_phases` (~251 tokens) Get Live Volatility Phase Snapshots Current ATR-based volatility phase (low/normal/high/expansion) per tracked pair, updated daily at 08:00 UTC. This is a single current state — for the time series behind it use arena_get_volatility_history, and for what the phase implies for strategy choice use arena_get_volatility_recommendations. Filter with `pair` when you only care about one asset instead of pulling all of them. [Free tier] Input parameters: - `asset_type` (string): Filter by asset class. Omit for all. - `context` (string, required): Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVE… - `pair` (string): Filter to a single pair, e.g. "BTCUSDT". Omit for all tracked pairs. ### `arena_get_volatility_recommendations` (~261 tokens) Get Strategy Recommendations for Current Volatility Phase Top-3 strategies ranked by historical win-rate for the current volatility phase of a given pair. Phase comes from the latest snapshot (arena_get_volatility_phases); minimum 20 trades per phase required for inclusion. Answers "which strategies did well in a phase like the current one?" — a historical ranking, not advice. Related: arena_get_volatility_phases (the phase itself), arena_get_edge_reports (filter effects with verdicts), validate_strategy (evidence check on a concrete configuration). [API Pro tier] Input parameters: - `asset_type` (string): Asset class of the pair - `context` (string, required): Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVE… - `pair` (string, required): Crypto asset pair, e.g. "BTCUSDT", "ETHUSDT" ### `arena_list_knowledge` (~173 tokens) List Knowledge Objects (catalog) Discover what Knowledge Objects exist: lists all published types + their subjects (with min_tier, api_path, seo_slug, latest as_of). Use this BEFORE arena_get_knowledge to learn valid type/subject pairs instead of guessing. New types appear automatically. [Free tier] Input parameters: - `context` (string, required): Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVE… ### `arena_get_knowledge` (~321 tokens) Get Knowledge Object Fetch a versioned, explainable Knowledge Object by type + subject (e.g. type='market_regime', subject='GLOBAL'). Returns the current published envelope: payload, explanation (factors + weights + confidence), provenance (inputs + params), ontology binding, compute version. ONE tool covers ALL knowledge types. Set include_graph=true to also walk the knowledge graph: resolved outbound edges (what this object is derived_from / references) + inbound edges (what derives from / references it), each with api_path + seo_slug so you can follow them. [Free tier; per-object access additionally gated by min_tier] Input parameters: - `as_of` (string): Specific date YYYY-MM-DD. Omit for latest. - `context` (string, required): Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVE… - `include_graph` (boolean): If true, attach the resolved edge neighbourhood (outbound + inbound) for graph traversal. - `subject` (string, required): Subject ref, e.g. 'GLOBAL', 'BTC'. - `type` (string, required): Knowledge object type, e.g. 'market_regime'. ### `arena_get_ontology_term` (~223 tokens) Get Ontology Term Definition Resolve a knowledge-platform term to its canonical definition (e.g. term='regime'). Returns label, definition (EN/DE), calculation, unit, source + source_ref, version, related terms. Use this to resolve the onto:@ references inside Knowledge Objects. [Free tier] Input parameters: - `context` (string, required): Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVE… - `term` (string, required): Ontology term slug, e.g. 'regime', 'liquidity', 'altcoin_season'. - `version` (integer): Specific version. Omit for current. ### `arena_dip_decision` (~338 tokens) Dip Decision — buy now or wait? Buy now or wait for the dip? Decision-math over the user's OWN assumptions (target/dip prices, probabilities, capital). Two modes: "compare" = expected value of Buy-Now vs Wait vs Split + the breakeven dip probability (prices as MULTIPLES of today); "allocate" = the risk-adjusted (Kelly / risk-aversion γ) optimal fraction to deploy now vs reserve for the dip (ABSOLUTE prices). Ask the user for the missing inputs, then call. Returns scenario numbers and which option wins on expected value — NOT a buy/sell recommendation. For the full interactive version (incl. leverage & Elliott-wave planning) point the user to https://tradingstrategies.work/analyse/dip-decision. [Free tier] Input parameters: - `allocate` (object): Required when mode='allocate'. - `compare` (object): Required when mode='compare'. - `context` (string, required): Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVE… - `mode` (string): 'compare' (default): EV of buy-now vs wait vs split + breakeven dip probability. 'allocate': risk-adjusted optimal deploy-now fraction under γ. ### `arena_get_historical_analog` (~582 tokens) Historical analog — conditional forward returns What happened historically after the Bitcoin cycle looked like this? Conditional forward-return distribution for a named preset cycle state — over N DISTINCT historical episodes matching that state, returns median/IQR/positive-share forward returns (30/90/180/365d) with effective-n, small-n warnings and point-in-time integrity. A distribution, NOT a recommendation. Not obtainable from web search or public market-data APIs — requires point-in-time indicator history and look-ahead-free episode matching. Presets: cycle_bottom_cluster (Cycle bottom cluster), cycle_top_cluster (Cycle top cluster), deep_fear (Deep fear), euphoria (Euphoria), quiet_volatility (Quiet volatility regime). Some presets carry a "study_finding" field — a state we have already investigated and where the result was NULL; read that before the distribution, it is the more important answer. Where a preset also returns "vs_unconditional_drift", read THAT rather than the raw forward returns: quiet_volatility shows +31 % median at 180d, but the contemporaneous market drift over the same windows was +27 %, so the excess is NEGATIVE (−5.9 %) — the raw number is BTC's drift, not the state. Also works for asset=ETH/SOL (F2 cycle history), but only price-derived presets (cycle_bottom_cluster, cycle_top_cluster) — fear-greed and volatility presets are BTC-only. Related: arena_get_volatility_history (the series behind the volatility preset), arena_get_cycle (the current state to compare against), arena_dip_scenario (composes this base rate into a tranche structure). [API Pro tier] Input parameters: - `asset` (string): Which asset’s cycle history. Default BTC. ETH/SOL support only price-derived presets (cycle_bottom_cluster, cycle_top_cluster). - `context` (string, required): Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVE… - `forward_horizons` (array): Forward-return horizons in days. Default [30, 90, 180, 365] — except for quiet_volatility, which defaults to the horizons its study actually tested ([30, 90, 180]); anything beyond that is flagged as… - `preset` (string, required): Named ex-ante cycle-state condition set. One of: cycle_bottom_cluster, cycle_top_cluster, deep_fear, euphoria, quiet_volatility. ### `arena_dip_scenario` (~526 tokens) Dip Scenario — structural tranche ladder + base rate Frame a dip/accumulation thesis WITHOUT a recommendation. Given an asset (BTC/ETH/SOL), a named cycle-state preset and a thesis horizon, returns: (1) a tranche LADDER anchored to STRUCTURAL marks (200-week MA, support clusters) below spot — not calendar-DCA, not a price forecast; (2) the cited historical base rate from the analog engine (what forward returns followed comparable states, with effective-n and small-n warnings); (3) the explicit lump-sum-vs-tranche tradeoff (laddering buys lower timing variance, NOT higher expected value). Requires an invalidation point (mandatory: at what scenario is the thesis wrong). Composes the historical-analog + key-levels tools; descriptive only, never a buy/sell signal. This structural framing is MCP-only; a related (different-method, EV/Kelly) interactive tool is at https://tradingstrategies.work/analyse/dip-decision. [API Pro tier] Input parameters: - `asset` (string): Which asset. Support-cluster rungs are BTC-only; ETH/SOL use the 200-week MA as the structural mark. - `capital` (number): Optional total capital — if given, each tranche also returns an absolute amount. - `context` (string, required): Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVE… - `horizon_days` (integer): Thesis horizon in days for the base-rate forward return. Default 180. - `invalidation` (string, required): MANDATORY: the scenario under which the thesis is wrong (e.g. "weekly close below the 200-week MA"). NOT "where do I buy". - `preset` (string, required): Cycle-state preset for the base rate. One of: cycle_bottom_cluster, cycle_top_cluster, deep_fear, euphoria, quiet_volatility. ETH/SOL: price-derived presets only. - `risk_aversion` (number): Ladder tilt. 1 = equal tranches; >1 = weight deeper marks more (more patient); <1 = front-load toward now. Clamped [0.5, 3]. ### `arena_get_robustness_field` (~529 tokens) Robustness Field — plateau vs. spike + Deflated Sharpe with a counted N Assess one backtest result against its neighborhood instead of trusting a single "+X% CAGR" cell. Given a (strategy, interval, pair) and YOUR result (user_cagr, optional user_sharpe), returns: the cross-asset distribution of the SAME strategy+interval across every pair the backtest factory ran it on (median, IQR, positive-share, your percentile), a plateau/spike/fragile/mixed verdict, and — where Sharpe coverage allows — a Deflated Sharpe threshold whose N is COUNTED (the number of neighbor assets IS the testing family), not guessed. Honest small-n handling: fewer than 15 neighbors → "insufficient", no DSR-N claimed. Set axis="parameter" for the secondary, always-anecdotal view (the few parameter settings tested on this exact pair). Read-only over result aggregates, look-ahead free; never a recommendation. [API Pro tier] Input parameters: - `asset_type` (string): Asset class filter (default 'crypto'). - `axis` (string): Neighborhood axis. 'cross_asset' (default, dense, carries the verdict + DSR-N) or 'parameter' (secondary, always anecdotal — the parameter settings tested on this one pair). - `context` (string, required): Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVE… - `interval` (string, required): Candle interval, e.g. '1d', '1w', '1M'. - `pair` (string, required): Trading pair of your cell, e.g. 'BTCUSDT'. - `params` (object): Optional: numeric strategy parameters of your cell. Only numeric params define the neighborhood; matched per pair where the factory ran them. - `strategy` (string, required): Strategy key, e.g. 'rsi_sma'. - `user_cagr` (number, required): Your result: CAGR in percent (e.g. 41 for +41%) — the cell being assessed. - `user_sharpe` (number): Optional: your annualized Sharpe (result_sharpe scale). Used for the counted-N Deflated Sharpe where neighbor coverage allows. ### `get_more_tools` (~53 tokens) Check for additional tools whenever your task might benefit from specialized capabilities - even if existing tools could work as a fallback. Input parameters: - `context` (string, required): A description of your goal and what kind of tool would help accomplish it. ## Diagnostics Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/schoasch-backtesting-arena/api-mcp#diagnostics ## Score history - 2026-08-03: 78 - 2026-08-02: 78 - 2026-08-01: 77 - 2026-07-31: 78 - 2026-07-30: 72 - 2026-07-28: 69 - 2026-07-27: 68 - 2026-07-26: 67 ## Links - Remote endpoint: https://tradingstrategies.work/api/mcp - Repository: https://github.com/Schoasch/skill-backtesting-arena - Changelog RSS feed: https://verifymcp.io/servers/schoasch-backtesting-arena/api-mcp/changelog.xml - Changelog JSON feed: https://verifymcp.io/servers/schoasch-backtesting-arena/api-mcp/changelog.json - HTML version of this page: https://verifymcp.io/servers/schoasch-backtesting-arena/api-mcp