Skip to main content
Glama

Cancel a running backtest

acubic_cancel_backtest
Idempotent

Cancels a backtest that is still running, like Cancel on acubic.ai: the allowance it used is returned and the previous saved result stays. Needs the run_id from acubic_run_backtest. To remove a strategy use acubic_delete_strategy.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "strategy_id": "<strategy_id>",
      "run_id": "<run_id>"
    },
    "name": "acubic_cancel_backtest"
  }
}

Input Schema

NameRequiredDescriptionDefault
localeNoThe language of this conversation.
run_idYesThe run_id acubic_run_backtest returned.
strategy_idYesThe strategy the run belongs to.

Output Schema

NameRequiredDescriptionDefault
errorNo
run_idNo
statusNo
refundedNoWhether the run's allowance was returned; null when not reported.
cancelledNo
strategy_idNo
cancelled_by_this_callNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

The annotations already declare non-read-only, non-destructive and idempotent, and the description adds real consequence detail beyond them: the allowance is returned and the previously saved result is preserved. That is exactly the side-effect context an agent needs. It omits the failure mode for an already-completed run, so it is not exhaustive.

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?

Three short sentences, front-loaded with the action and outcome before the dependency and the alternative. The 'like Cancel on acubic.ai' analogy is mildly decorative but does reinforce the allowancing semantics, so it earns its place.

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?

With an output schema present, full annotation coverage and complete parameter documentation, the description only needs to convey the effect and the routing. It does both, so nothing an agent needs in order to call this correctly is missing.

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 coverage is 100%, so strategy_id, run_id and locale are already documented in the input schema. The description only restates the provenance of run_id, which the schema already says. Baseline 3 is appropriate when the schema carries the parameter burden.

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 precise verb and resource ('Cancels a backtest that is still running') and immediately clarifies the scope condition 'still running'. It is clearly distinguishable from acubic_delete_strategy, which it names explicitly, and from acubic_run_backtest, which it consumes.

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?

It tells the agent that the target must be a running backtest and that the run_id must come from acubic_run_backtest, and it routes the different goal of removing a strategy to acubic_delete_strategy. It stops short of saying what happens if the run has already finished or failed, which would fully close the when-not gap.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources