Skip to main content
Glama

Backtesting Arena

by io.github.Schoasch

Subscribe to Arena-Pulse Score Threshold Crossings

arena_subscribe_pulse_changes

Notify me when market heat crosses a threshold? Fires when the daily 0–100 Arena-Pulse score crosses threshold_above (upward) or threshold_below (downward). At least one threshold is required. For the current score without subscribing, call arena_get_pulse. 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
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).
threshold_aboveNoFire when score rises across this value.
threshold_belowNoFire when score falls across this value.

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

TDQS

A4.7/5.0
Behavior5/5

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

With no annotations provided, the description carries the full burden and meets it. It discloses that this creates a standing subscription, that it does not return a value now, that updates arrive via polling or webhook, that it can auto-deactivate via expires_at, and the quota limits per tier (max 3 Pro, 20 Power). No contradiction with annotations since none exist.

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 user-question framing and the core firing condition before lifecycle details. Dense but every sentence contributes; the only mild inefficiency is some reiteration of the read-tool alternative in two places, which is a minor redundancy rather than waste.

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?

Complete for a 5-parameter subscription tool with no output schema: the description explicitly addresses the 'no immediate return value' behavior and points to the polling and cancellation siblings. All parameters are covered by the schema plus description. The only gap is a missing description of the fired update payload format, which the polling tool's schema would presumably document.

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

Parameters4/5

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

Schema coverage is 100%, so the schema names and describes each parameter. The description adds genuine value beyond the schema: it clarifies that at least one threshold is required, that webhook_url is required only for delivery_method=webhook and ignored otherwise, and that expires_at causes auto-deactivation. This enriches the otherwise bare schema entries.

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 (subscribe) and resource (Arena-Pulse score threshold crossings), with exact firing conditions for threshold_above (upward) and threshold_below (downward). Explicitly contrasts with the arena_get_pulse sibling for reading the current value, so an agent can distinguish subscription from read tools.

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 explicit when-to-use guidance: 'For the current score without subscribing, call arena_get_pulse' and 'For the CURRENT value instead of a change notification, call the matching read tool.' Names the lifecycle siblings (arena_check_subscription_updates, arena_cancel_subscription) and states the 'At least one threshold is required' precondition.

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