Skip to main content
Glama

Backtesting Arena

by io.github.Schoasch

Subscribe to BTC Cycle Band Changes

arena_subscribe_cycle_changes

Notify me when the cycle band changes? Bands: (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 Schema

TableJSON Schema
NameRequiredDescriptionDefault
bandsNoFilter to bands of interest. Default: any change triggers.
expires_atNoISO-8601 timestamp after which the subscription auto-deactivates. Omit to keep it active until cancelled.
webhook_urlNoHTTPS endpoint we POST to. Required when delivery_method=webhook, ignored otherwise.
delivery_methodNoHow updates reach you: 'polling' (default — collect via arena_check_subscription_updates) or 'webhook' (we POST to your URL).

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. Changed3 schema fields changed
    • changedInput schema / properties / delivery_method / description
      Previous value: -"'polling' (default) or 'webhook'."New value: +"How updates reach you: 'polling' (default — collect via arena_check_subscription_updates) or 'webhook' (we POST to your URL)."
    • changedInput schema / properties / expires_at / description
      Previous value: -"ISO timestamp; subscription auto-deactivates after this."New value: +"ISO-8601 timestamp after which the subscription auto-deactivates. Omit to keep it active until cancelled."
    • changedInput schema / properties / webhook_url / description
      Previous value: -"HTTPS URL — required when delivery_method=webhook."New value: +"HTTPS endpoint we POST to. Required when delivery_method=webhook, ignored otherwise."
  3. First observed

TDQS

A4.3/5.0
Behavior4/5

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

No annotations are provided, so the description carries the full burden. It discloses that the tool creates a standing subscription and does not return a value immediately, explaining the async nature and how updates are delivered. It also mentions tier limits (max 3/20 subscriptions), which is useful behavioral context. However, it does not specify what the immediate return value is (e.g., subscription ID) or the details of the notification payload, which are minor gaps.

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 front-loaded with the core purpose and then covers lifecycle and alternatives. It is somewhat verbose with redundancy: the same 'call arena_get_cycle for current value' point appears twice. Still, every sentence carries useful information about usage, limits, and mechanics, so it is effective despite being a bit wordy.

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?

For a subscription tool with no output schema and all parameters documented, the description covers the key aspects: what it does, how to receive updates, how to end it, and alternatives. It lacks details on the immediate response format and the exact payload of a fired notification, which could be relevant for agents, but overall it gives enough for correct invocation.

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%, so the baseline is 3. The description adds some context for the 'bands' parameter ('Optional bands filter restricts to specific target bands') and mentions delivery methods, but these are largely covered by the schema. It does not add substantial semantic value beyond what the JSON schema already describes.

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 tool subscribes to cycle band changes and lists the bands. It distinguishes itself from arena_get_cycle (for current value) and other subscription tools by specifying the exact resource and event. The phrasing 'Notify me when the cycle band changes' is a specific verb+resource that immediately conveys purpose.

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 explicitly tells the agent when to use this tool vs. alternatives: 'For the current band without subscribing, call arena_get_cycle' and 'For the CURRENT value instead of a change notification, call the matching read tool.' It also explains how to collect updates (polling or webhook) and terminate the subscription (arena_cancel_subscription), giving complete usage context.

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