Skip to main content
Glama

Get a backtest result

acubic_get_backtest
Read-onlyIdempotent

Returns the latest saved walk-forward backtest of one strategy: assumptions, CAGR, volatility, Sharpe and Sortino, maximum drawdown and total return against the S&P 500 (SPY), yearly returns, drawdown episodes and last holdings; include adds the equity curve. Figures are hypothetical and carry a disclosure. Read it once a run has finished; to follow a run use acubic_get_backtest_status.

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>"
    },
    "name": "acubic_get_backtest"
  }
}

Input Schema

NameRequiredDescriptionDefault
localeNoThe language of this conversation.
run_idNoA finished run of acubic_run_backtest to read.
includeNoequity_series: curves vs SPY (up to 200 points); performance_summary: report rows. detailed includes both.
strategy_idYesThe strategy whose latest saved backtest to read.
response_formatNoconcise

Output Schema

NameRequiredDescriptionDefault
errorNo
backtestNo
truncatedNo
disclosureNo
equity_seriesNoinclude equity_series (or detailed): the daily curves indexed near 100 at the start, evenly downsampled (first and last kept).
performance_summaryNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so safety is covered. The description still adds real behavioral context: results are 'latest saved' rather than live, figures are hypothetical and carry a disclosure, and the include parameter can expand the payload with the equity curve. It does not state size/volume limits or what happens when no saved backtest exists yet.

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 verb and returned fields, then the include behavior, then the caveat, then the routing hint. The field list is dense but justified for a rich result payload; a semicolon-heavy middle clause makes it slightly harder to scan than it needs to be.

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?

An output schema exists, so the field enumeration is partly redundant, but it usefully tells the agent up front what class of result to expect and warns that figures are hypothetical. Combined with the finished-run precondition and the status sibling, an agent has enough to invoke this correctly; only the run_id-versus-strategy_id selection is left implicit.

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 80%, so most parameters are self-documenting and the baseline is 3. The description adds only marginal meaning — 'include adds the equity curve' — and actually under-describes the schema, which also offers performance_summary; it says nothing about run_id selecting a specific finished run versus the default latest-saved behavior, nor about locale or response_format.

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 — 'Returns the latest saved walk-forward backtest of one strategy' — and enumerates exactly what the payload contains (CAGR, volatility, Sharpe/Sortino, max drawdown, SPY comparison, yearly returns, drawdown episodes, holdings). It also names the sibling it is not (acubic_get_backtest_status), so an agent can distinguish a result fetch from a status poll without opening either 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?

Explicit timing condition ('Read it once a run has finished') plus a named alternative for the other case ('to follow a run use acubic_get_backtest_status'). This is the when-to-use / when-not-to-use pairing done cleanly.

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