Skip to main content
Glama

Backtesting Arena

by io.github.Schoasch

Share a Grid Backtest

arena_share_grid_backtest

Want a public link for a grid result? Publishes a read-only snapshot page (with OG preview image) for one of YOUR saved grid backtest runs and returns its URL. Pass the run_id you got back from arena_run_grid_backtest (every authenticated run is saved automatically). The page shows the numbers the engine actually computed — this tool takes no result values, so shared pages cannot carry fabricated figures. Shares are permanent snapshots; language picks the page copy (en default). [Free tier]

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
run_idYesId of one of your saved grid backtest runs (returned by arena_run_grid_backtest).
languageNoPage language of the share. Default 'en'.

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"
-}
    • changedInput schema / required
      Previous value: -[
-  "run_id",
-  "context"
-]New value: +[
+  "run_id"
+]
  2. Added

TDQS

A4.1/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 behavioral burden. It discloses that the share is read-only, permanent ('Shares are permanent snapshots'), includes an OG preview image, does not accept result values (so pages cannot contain fabricated figures), and that language selects the page copy. The '[Free tier]' hint touches on access constraints. It does not mention auth requirements or rate limits, but for a sharing action the disclosed permanence and integrity guarantees are substantial.

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?

The description is three sentences, front-loaded with the purpose and output. It includes extra value like 'OG preview image', 'permanent snapshots', 'no result values', and '[Free tier]' without being verbose. The conversational opening is slightly informal but not wasteful. Every sentence adds information relevant to the call.

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?

Given there is no output schema, the description explicitly states the return is a URL. It covers the input source (run_id from arena_run_grid_backtest), the nature of the share (read-only, permanent), language behavior, and integrity guarantees. It does not mention error cases or rate limits, but for a sharing action it is complete enough for an agent to call it correctly and understand 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 description coverage is 100%: both run_id and language have descriptive properties in the schema. The description reaffirms run_id as 'the run_id you got back from arena_run_grid_backtest' and adds that 'language picks the page copy', but it does not add syntax or format details beyond the schema. The baseline of 3 is appropriate because the schema already documents the parameters well.

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 states a specific verb ('publishes') and resource ('read-only snapshot page ... for one of YOUR saved grid backtest runs') and clearly indicates the output ('returns its URL'). It is distinguished from sibling tools by focusing on the sharing act, not retrieval or analysis. The inclusion of 'read-only' and 'OG preview image' adds clarity about what is produced.

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

Usage Guidelines4/5

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

The opening question 'Want a public link for a grid result?' sets the context, and the explicit instruction 'Pass the run_id you got back from arena_run_grid_backtest' provides a direct usage path. It implies the tool is for sharing your own saved runs, and the note 'every authenticated run is saved automatically' reinforces that prerequisite. However, it does not explicitly contrast with sibling tools like arena_get_shared_backtest, which might retrieve an existing share.

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