Skip to main content
Glama

Get a strategy

acubic_get_strategy
Read-onlyIdempotent

Returns one saved strategy: holdings and weights, its settings (experience and risk level, ranking, weighting, asset count, filters, locks), data date, the summary of its latest saved backtest and its broker connection. It also accepts the build_id of a finished build (while it runs use acubic_get_build_status). Figures are hypothetical and carry a disclosure. For the full backtest use acubic_get_backtest.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "acubic_get_strategy"
  }
}

Input Schema

NameRequiredDescriptionDefault
localeNoThe language of this conversation.
build_idNoA build_id of acubic_create_strategy; resolves to the strategy once saved.
strategy_idNoThe strategy to read.
holdings_limitNoHoldings to return.
response_formatNoconcise

Output Schema

NameRequiredDescriptionDefault
liveNoNull when no broker is connected.
buildNoA build that has not finished: poll again after poll_after_seconds.
errorNo
holdingsNo
settingsNo
strategyNo
truncatedNo
disclosureNo
generationNo
holdings_totalNo
latest_backtestNo
needs_attentionNo

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 establish that this is a read-only, idempotent, non-destructive operation. The description adds useful behavioral context: the response includes hypothetical figures with a disclosure, build_id resolves to a strategy only once saved, and running builds belong to a different tool. It does not describe error behavior when no identifier is supplied.

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 dense but front-loaded, starting with the primary return value and then covering settings and backtest details. Every sentence adds routing or behavioral information, though the long parenthetical list of settings could be tightened.

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?

Given the output schema and strong annotations, the description covers the key behavioral facts an agent needs: what is returned, how build_id works, and which sibling tools handle running builds and full backtests. The only notable omission is that the description does not state that a strategy_id or build_id is required in practice.

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 description coverage is high at 80%, so the baseline is 3. The description adds meaning beyond the schema by explaining that build_id is accepted only for a finished build and resolves to the saved strategy, and by clarifying what strategy data is returned. It does not elaborate on holdings_limit or response_format behavior.

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 uses a specific verb and resource: it returns one saved strategy, and it enumerates the returned contents including holdings, settings, data date, latest backtest summary, and broker connection. It also distinguishes itself from acubic_get_build_status for in-progress builds and acubic_get_backtest for full backtest data.

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?

The description clearly routes agents to acubic_get_build_status while a build is running and to acubic_get_backtest for the full backtest. It also explains that build_id can be used once a build is saved. It does not explicitly state that one of strategy_id or build_id should be supplied, which is a minor 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