Skip to main content
Glama
Sign In

Backtesting Arena

by io.github.Schoasch
OverviewDiscussionsAdmin

List Available Trading Strategies

arena_list_strategies
Read-only

Which strategies can I backtest here? Lists all backtest strategies (key, label, plan, supported asset classes, primary indicators, free_params = number of user-tunable parameters incl. mode switches). Filterable by asset class and plan. Use this before calling arena_run_backtest to discover valid strategy names. Entries deprecated for an asset class stay listed (historical results depend on them) and carry deprecated_for + deprecation {since, reason} — do NOT call arena_run_backtest or validate_strategy for those combinations, they return 400. [Free 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_strategies"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNoLocalized names/taglines. Default 'en'.
planNoFilter to strategies of this plan tier.
asset_classNoFilter to strategies supporting this asset class (crypto or tokenized_rwa).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • removedInput schema / additionalProperties
      Removed value: -false
  2. 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"
-]
  3. Changed2 schema fields changed
    • changedInput schema / properties / asset_class / description
      Previous value: -"Filter to strategies supporting this asset class (crypto only)."New value: +"Filter to strategies supporting this asset class (crypto or tokenized_rwa)."
    • changedInput schema / properties / asset_class / enum
      Previous value: -[
-  "crypto"
-]New value: +[
+  "crypto",
+  "tokenized_rwa"
+]
  4. Changed2 schema fields changed
    • changedInput schema / properties / asset_class / description
      Previous value: -"Filter to strategies supporting this asset class."New value: +"Filter to strategies supporting this asset class (crypto only)."
    • changedInput schema / properties / asset_class / enum
      Previous value: -[
-  "crypto",
-  "stock",
-  "etf",
-  "commodities",
-  "forex"
-]New value: +[
+  "crypto"
+]
  5. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations only declare readOnlyHint=true; the description adds substantial beyond that — deprecated entries remain listed, carry deprecated_for + deprecation {since, reason}, and cause 400s downstream. It also discloses the response field set and the meaning of free_params, which matters for the follow-up backtest call.

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

Conciseness4/5

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

Front-loaded with the intent question, then field list, then workflow guidance, then the deprecation warning — good ordering with no wasted prose. Slightly dense in the parenthetical field enumeration, but every clause carries operational information.

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?

No output schema exists, and the description compensates by describing the returned entry shape and deprecation metadata. Combined with the 400-failure warning and the pre-backtest workflow role, an agent has everything needed to call this correctly and interpret the result.

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 three params enum-documented, so the schema does the heavy lifting. The description reinforces the asset_class and plan filters semantically ("Filterable by asset class and plan") but says nothing about lang, which lives only in the schema. Baseline 3 is appropriate.

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 all backtest strategies") and immediately enumerates the returned fields (key, label, plan, asset classes, indicators, free_params). It is unmistakable next to siblings like arena_get_strategy_performance or arena_list_backtests.

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?

Explicitly prescribes the call order ("Use this before calling arena_run_backtest to discover valid strategy names") and states a hard exclusion: do NOT call arena_run_backtest or validate_strategy for deprecated-for-asset-class combinations because they return 400. When-not guidance with a named sibling and a concrete failure mode.

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
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.

Resources