Skip to main content
Glama

Backtesting Arena

by io.github.Schoasch
OverviewDiscussionsAdmin

Subscribe to Strategy Signal Alerts

arena_subscribe_signal_alerts

Notify me when this signal flips? Fires when an existing Ampel-Config's signal flips (BUY ↔ SELL). Prerequisite: the user must have created that ampel-config in the web UI (/dashboard/ampel) — pass its UUID here; this tool cannot create one. Optional signal_types filter narrows to BUY-only or SELL-only. For the current signal state without subscribing, call arena_get_signal_status. 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.
signal_typesNoOptional filter. Default: both BUY and SELL fire.
ampel_config_idYesUUID einer existierenden ampel_configs-Row im gleichen User-Account.
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.

  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: -[
-  "ampel_config_id",
-  "context"
-]New value: +[
+  "ampel_config_id"
+]
  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.8/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. It discloses that the tool creates a standing subscription, does not return a value immediately, and fires on signal flips. It also details tier limits ('[API Pro tier and up — max 3 active subscriptions for Pro, 20 for Power]') and the prerequisite about user-created ampel-configs. No contradictions with any structured data.

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 dense but each sentence serves a purpose: it opens with the core use case, then covers prerequisites, filtering, return behavior, alternatives, and tier limits. It doesn't waste words on fluff. It's longer than average, but for a subscription tool with multiple parameters and lifecycle considerations, the length is justified and front-loaded with the primary scenario.

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?

The description is complete for a subscription tool with no output schema. It explicitly states what the tool does not return (no immediate value), how to retrieve updates (polling or webhook), how to terminate (arena_cancel_subscription), and the tier constraints. It leaves no ambiguity about the tool's lifecycle, which is critical for correct usage.

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?

The schema already documents all 5 parameters (100% coverage), so the baseline is 3. The description adds meaningful context: it clarifies that signal_types narrows to BUY-only or SELL-only, explains the delivery_method options explicitly, notes webhook_url is only required when delivery_method=webhook, and describes expires_at behavior. It also explains ampel_config_id as referring to an existing config in the same user account, which adds value beyond the schema's brief description.

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 precise purpose: 'Notify me when this signal flips?' and specifies the trigger condition ('when an existing Ampel-Config's signal flips (BUY ↔ SELL)'). It clearly identifies the resource (signal alerts on an ampel-config) and the action (subscribe). It also differentiates itself from siblings like arena_get_signal_status (current state) and arena_cancel_subscription, so an agent can tell them apart.

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 explicit guidance: it is a standing subscription for change notifications, contrasting with 'For the CURRENT value instead of a change notification, call the matching read tool.' It also explains the prerequisite that the ampel-config must exist in the web UI, and describes the delivery options (polling vs webhook) with references to arena_check_subscription_updates and arena_cancel_subscription. This covers when to use it and provides alternatives.

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