Backtesting Arena

List Your Backtests

arena_list_backtests

Read-only

Which backtests have I run? 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]

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "arena_list_backtests"
  }
}

Input Schema

Name	Required	Description
`pair`	No	Filter by pair symbol, e.g. BTCUSDT. Omit for all.
`limit`	No	Page size, max 100, default 50.
`offset`	No	Rows to skip for paging; default 0.
`interval`	No	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 alignments is used. Measured on our own corpus, the choice of alignment alone moves CAGR by 6.66 pp on average (max 12.30). Treat differences below that as not distinguishable — 1d/2d/3d behaved as one block in our tests, not a ranking.
`strategy`	No	Filter by strategy key, e.g. 'rsi_sma'. Omit for all.
`asset_type`	No	Filter by asset class, e.g. 'crypto'. Omit for all.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 29, 2026
- removedInput schema / additionalProperties
```
Removed value: -false
```
- addedInput schema / properties / offset / maximum
```
Added value: +9007199254740991
```

Changed3 schema fields changedAug 25, 2026

addedInput schema / additionalProperties
```
Added value: +false
```

removedInput schema / properties / context

Removed value: -{
-  "description": "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). NEVER use first person ('I', 'we', 'you') - maintain third-person perspective. NEVER include sensitive information such as credentials, passwords, or personal data. Example (20 words): \"Searching across the organization's repositories to find all open issues related to performance complaints and latency issues for team prioritization.\"",
-  "type": "string"
-}

removedInput schema / required
```
Removed value: -[
-  "context"
-]
```

Changed1 schema field changedJul 31, 2026

changedInput schema / properties / interval / description

Previous value: -"Filter by candle interval. Omit for all."New value: +"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 alignments is used. Measured on our own corpus, the choice of alignment alone moves CAGR by 6.66 pp on average (max 12.30). Treat differences below that as not distinguishable — 1d/2d/3d behaved as one block in our tests, not a ranking."

Changed1 schema field changedJul 31, 2026

changedInput schema / properties / interval / enum

Previous value: -[
-  "1d",
-  "1w",
-  "1M"
-]New value: +[
+  "1d",
+  "2d",
+  "3d",
+  "1w",
+  "1M"
+]

Changed6 schema fields changedJul 27, 2026

addedInput schema / properties / asset_type / description

Added value: +"Filter by asset class, e.g. 'crypto'. Omit for all."

addedInput schema / properties / interval / description

Added value: +"Filter by candle interval. Omit for all."

changedInput schema / properties / limit / description

Previous value: -"Max 100, default 50."New value: +"Page size, max 100, default 50."

addedInput schema / properties / offset / description

Added value: +"Rows to skip for paging; default 0."

addedInput schema / properties / pair / description

Added value: +"Filter by pair symbol, e.g. BTCUSDT. Omit for all."

addedInput schema / properties / strategy / description

Added value: +"Filter by strategy key, e.g. 'rsi_sma'. Omit for all."

Changed1 schema field changedJul 24, 2026

changedInput schema / properties / asset_type / enum

Previous value: -[
-  "crypto"
-]New value: +[
+  "crypto",
+  "tokenized_equity",
+  "tokenized_etf",
+  "commodities"
+]

Changed1 schema field changedJul 14, 2026

changedInput schema / properties / asset_type / enum

Previous value: -[
-  "crypto",
-  "stock",
-  "etf",
-  "commodities",
-  "forex"
-]New value: +[
+  "crypto"
+]

First observedJul 13, 2026

TDQS

A4.5/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

readOnlyHint=true already covers the safety profile, and the description still adds real context: newest-first ordering, authenticated-user-only scoping, pagination via limit+offset, and the ['API Pro tier'] access requirement. It stops short of describing empty-result or paging edge behavior, so a 4 rather than a 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The core question is front-loaded, followed by scope, payload, next-step routing, exclusivity, paging and tier in that order. No sentence is redundant: each one either scopes the call or redirects to a sibling.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description compensates by enumerating the returned fields (id, strategy, pair, interval, date range, headline metrics) and stating ordering and paging. Combined with the annotations and full schema coverage, an agent has everything needed to call and consume this tool correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and the schema already documents every filter; the description only echoes 'Paginated via limit + offset' and lists which fields appear per run. That is a modest reinforcement rather than new parameter meaning, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Lists the backtest runs belonging to the authenticated user') plus ordering and per-row contents. The 'Which backtests have I run?' framing plus the explicit ownership scope makes it trivially distinguishable from arena_get_winners and arena_list_strategies.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit when-to-use ('Use it to find a run_id'), names both follow-on tools (arena_get_backtest for detail, arena_get_backtest_trades for trades), and pre-empts the most likely confusion by routing public cross-user data to arena_get_winners.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Backtesting Arena tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.