Skip to main content
Glama

Get a strategy's historical performance

acubic_get_strategy_history
Read-onlyIdempotent

Returns the Historical tab of one saved strategy: its saved weights bought and held over 1 month to 5 years, with return, CAGR, volatility, Sharpe and maximum drawdown beside the S&P 500 or a custom benchmark, and the daily series. Hypothetical, with a disclosure. For the walk-forward test use 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>"
    },
    "name": "acubic_get_strategy_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
localeNoThe language of this conversation.
horizonNoDefaults to 1y, as on acubic.ai.
strategy_idYesThe saved strategy.
response_formatNoconcise
custom_benchmarkNoUp to 10 instruments with weights.

Output Schema

NameRequiredDescriptionDefault
as_ofNo
basisNo
errorNo
seriesNo
horizonNonull when the strategy has no horizon figures (metrics are then the generation's own).
metricsNoFractions: total_return, cagr, volatility, max_drawdown (zero or negative); sharpe_ratio a ratio. benchmark is the S&P 500 (SPY).
horizonsNodetailed only: every horizon's figures.
open_urlNo
truncatedNo
disclosureNo
strategy_idNo
metrics_sourceNo
custom_benchmarkNo
horizons_availableNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and non-destructive, so the safety profile is covered. The description adds meaningful context beyond them: results are 'Hypothetical, with a disclosure', the right-hand side is the S&P 500 unless a custom benchmark is supplied, and the daily series is included. It does not discuss latency or caching, but for a read-only analytics tool that is minor.

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 purpose, followed by the output content, a caveat sentence, and a routing sentence. The metric list is long but each item is informative. Slightly dense as a single compound sentence, but no sentence is filler.

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, so return values need not be spelled out, yet the description still summarizes them at a useful level. Combined with the default-benchmark hint and the sibling routing, an agent has everything needed to call this correctly for a read-only, single-required-parameter tool.

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?

Schema coverage is 80%, so the baseline is 3, and the description adds genuine meaning on top: it defines the horizon span ('1 month to 5 years') and states that the default comparison is the S&P 500 versus a custom benchmark. It says nothing about locale or response_format, which keeps it from a 5.

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 Historical tab of one saved strategy') and immediately scopes it: saved weights bought and held, 1m–5y horizons, benchmark comparison, daily series. It is clearly distinguishable from a walk-forward backtest because the description names that distinction explicitly.

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?

Provides explicit routing to a sibling: 'For the walk-forward test use acubic_get_backtest.' That is a real when-to-use signal. It stops short of stating prerequisites (e.g. the strategy must exist and be saved) or when-not-to-use cases beyond the backtest alternative, so it is not a full 5.

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