Skip to main content
Glama

Backtesting Arena

by io.github.Schoasch

List Your Backtests

arena_list_backtests

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]

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pairNoFilter by pair symbol, e.g. BTCUSDT. Omit for all.
limitNoPage size, max 100, default 50.
offsetNoRows to skip for paging; default 0.
intervalNoFilter 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.
strategyNoFilter by strategy key, e.g. 'rsi_sma'. Omit for all.
asset_typeNoFilter by asset class, e.g. 'crypto'. Omit for all.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed3 schema fields changed
    • 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"
-]
  2. Changed1 schema field changed
    • 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."
  3. Changed1 schema field changed
    • changedInput schema / properties / interval / enum
      Previous value: -[
-  "1d",
-  "1w",
-  "1M"
-]New value: +[
+  "1d",
+  "2d",
+  "3d",
+  "1w",
+  "1M"
+]
  4. Changed6 schema fields changed
    • 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."
  5. Changed1 schema field changed
    • changedInput schema / properties / asset_type / enum
      Previous value: -[
-  "crypto"
-]New value: +[
+  "crypto",
+  "tokenized_equity",
+  "tokenized_etf",
+  "commodities"
+]
  6. Changed1 schema field changed
    • changedInput schema / properties / asset_type / enum
      Previous value: -[
-  "crypto",
-  "stock",
-  "etf",
-  "commodities",
-  "forex"
-]New value: +[
+  "crypto"
+]
  7. First observed

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations provided, the description carries the full burden of behavior disclosure. It discloses the operation is a read-only list ('Lists the backtest runs'), scopes results to the authenticated user, describes ordering ('newest first'), and states the tier ('API Pro'). It does not explicitly say there are no side effects, but 'list' implies a read. It could have noted that no mutation occurs or described auth failure behavior, but overall it provides sufficient behavioral context.

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 description is three sentences with no filler. The opening question 'Which backtests have I run?' immediately orients the agent, followed by the core purpose, usage flow, scope, and pagination note. Every clause earns its place, and the structure is front-loaded with the most critical information.

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

Completeness4/5

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

As a list tool with no output schema, the description compensates by listing the fields returned (id, strategy, pair, interval, date range, headline metrics), pagination parameters, scope, and related tools. It does not describe error or empty-result behavior, but that is a minor gap given the tool's simplicity and the absence of annotations. The mention of the API tier and the authenticated-user scope adds context. Overall, it is near-complete for its purpose.

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%, with all six parameters already described in the input schema (e.g., pair filter, limit max 100, offset default 0, interval enum, strategy, asset_type). The tool description adds only 'Paginated via limit + offset', which reinforces but does not extend beyond schema. Since coverage is high, the baseline is 3 and the description adds no new parameter meaning.

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?

The description clearly states the verb 'list' and the resource 'backtest runs', specifies the scope 'belonging to the authenticated user', and lists the fields returned (id, strategy, pair, interval, date range, headline metrics). It explicitly differentiates from sibling tools by naming arena_get_backtest for detail and arena_get_winners for the public leaderboard, so an agent can distinguish it without ambiguity.

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?

The description gives direct usage guidance: 'Use it to find a run_id, then call arena_get_backtest for its detail or arena_get_backtest_trades for the individual trades.' It also states when not to use it ('Only your OWN runs; for the public cross-user leaderboard use arena_get_winners') and mentions pagination via limit+offset. This is explicit and actionable.

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

All Backtesting Arena toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.6/5.0
Disambiguation2/5

Many tools cover overlapping market indicators (e.g., cycle state, pulse, bullmarket ampel, volatility phases) and several share similar get_*_history patterns, which could cause an agent to select the wrong one. However, each tool has detailed descriptions with explicit references to related tools to reduce ambiguity.

Naming Consistency3/5

Tool names generally follow a verb_noun pattern (arena_get_*, arena_list_*, arena_run_*, arena_subscribe_*), but there are inconsistencies such as 'validate_strategy' (no arena_ prefix), 'arena_status' (not a clear verb_noun), and variations like 'arena_run_grid_backtest' vs 'arena_run_backtest'.

Tool Count2/5

With 84 tools, the server is heavily over-scoped for a typical MCP server, likely causing navigation and selection overhead. While the domain (crypto backtesting and analytics) is broad, 84 tools exceed reasonable coherence and impose a high cognitive load.

Completeness4/5

The tool surface covers a wide range of analytics (market indicators, backtesting, validation, alerts, subscriptions, reports) with few obvious dead ends. Minor gaps exist like lack of direct portfolio management or strategy editing, but core workflows are well covered.

Resources