Skip to main content
Glama

Backtesting Arena

by io.github.Schoasch

Cancel Subscription

arena_cancel_subscription

Stop this alert? Deactivates one subscription by id, so it stops firing and frees a slot against the per-tier limit. Returns the deactivated subscription. Idempotent — cancelling an already-cancelled one is a no-op, not an error. Get ids from arena_list_subscriptions. Undelivered updates already queued are not removed. [API Pro tier]

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
subscription_idYesSubscription id returned by arena_subscribe_*

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: -[
-  "subscription_id",
-  "context"
-]New value: +[
+  "subscription_id"
+]
  2. First observed

TDQS

A4.9/5.0
Behavior5/5

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

With no annotations provided, the description carries full responsibility for behavioral disclosure. It covers: the side effect of freeing a slot, return value ('Returns the deactivated subscription'), idempotence, and the nuance that undelivered queued updates are not removed. It also mentions the API tier requirement. This is a thorough disclosure of behavior beyond the basic action.

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 moderately wordy but information-dense. The opening question 'Stop this alert?' is slightly informal and could be omitted, but it frames the intent well. Each subsequent sentence adds distinct value (action, slot implication, return, idempotence, id source, queued updates, tier). It is front-loaded with the core action before the details. A 4 reflects minor redundancy, not a significant flaw.

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?

For a single-parameter tool with no output schema, this description is exceptionally complete. It explains the return type, idempotence, side effects (slot freeing), the non-removal of queued updates, and the tier requirement. It also points to the correct sibling for id retrieval. An agent has all the information needed to call the tool correctly and interpret the result.

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

Parameters5/5

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

The schema already describes subscription_id as 'Subscription id returned by arena_subscribe_*', and the description adds a more practical retrieval source: 'Get ids from arena_list_subscriptions'. This is valuable because list_subscriptions is the natural place to get existing subscriptions to cancel, whereas arena_subscribe_* returns ids only at creation time. The description enhances the parameter's meaning beyond the schema.

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 opens with a user-oriented question 'Stop this alert?' and then states the core action: 'Deactivates one subscription by id, so it stops firing'. This clearly identifies the verb (deactivate) and resource (subscription by id), and it explicitly mentions freeing a slot against the per-tier limit, distinguishing it from getter siblings like arena_list_subscriptions or arena_check_subscription_updates. No ambiguity remains about what the tool does.

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 direct guidance: 'Get ids from arena_list_subscriptions' tells the agent exactly where to obtain the subscription_id parameter. It also explains the idempotent behavior ('cancelling an already-cancelled one is a no-op'), which informs when it is safe to call repeatedly, and notes that queued updates are not removed, setting expectations. Alternatives are implicitly clear since this is the only cancellation tool among the siblings.

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