Skip to main content
Glama

Check a backtest's progress

acubic_get_backtest_status
Read-onlyIdempotent

Checks a run of acubic_run_backtest without opening a card: percent done and poll_after_seconds, then the headline figures (hypothetical, with a disclosure). A run that failed or was cancelled is an error and nothing was charged. Use it to wait; read the full result once with acubic_get_backtest.

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_get_backtest_status"
  }
}

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
backtestNo
disclosureNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), and the description goes well beyond them: it discloses the response shape, that reported figures are hypothetical and carry a disclosure, that failed/cancelled runs surface as errors, and that nothing is charged in that case. Those billing and error semantics are exactly the behavioral context annotations cannot express.

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 sentences, front-loaded with the action and return values, then error behavior, then routing. Every sentence earns its place, though the parenthetical '(hypothetical, with a disclosure)' and 'without opening a card' make the first sentence slightly dense for a first read.

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?

An output schema exists, yet the description still covers the essentials an agent needs for a polling loop: what comes back, the suggested poll interval, what counts as an error, and where to go for the full result. Nothing needed 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 description coverage is 100%, so run_id, strategy_id, and locale are already documented. The description references 'a run' and ties it back to acubic_run_backtest, but adds no detail on the strategy_id/run_id pairing or the locale parameter beyond what the schema provides, so the baseline 3 applies.

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 and resource ('Checks a run of acubic_run_backtest') and immediately names what it returns (percent done, poll_after_seconds, headline figures). It explicitly distinguishes itself from two siblings by name, so an agent can tell it apart from acubic_run_backtest and acubic_get_backtest without opening any schema.

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?

'Use it to wait; read the full result once with acubic_get_backtest' gives both the condition for using this tool (polling while a run is in flight) and the explicit alternative for the other case. The distinction from acubic_get_backtest is unambiguous and actionable.

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