Skip to main content
Glama

Project a strategy (scenario simulation)

acubic_project_strategy
Read-onlyIdempotent

Runs a Monte Carlo of 500 paths over 1, 3, 5 or 10 years for one saved strategy, from its walk-forward backtest (the AI Scenario Simulation of acubic.ai): bear case (5th percentile), median, bull case (95th) and the percentile fan. Hypothetical, with a disclosure. Paid plans only. For past results 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_project_strategy"
  }
}

Input Schema

NameRequiredDescriptionDefault
localeNoThe language of this conversation.
horizonNoHow far ahead to simulate.3y
strategy_idYesThe saved strategy to project.
response_formatNoconcise

Output Schema

NameRequiredDescriptionDefault
errorNo
truncatedNo
disclosureNo
projectionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/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 the safety profile is covered. The description adds genuinely new behavior: fixed 500-path simulation, the forward-looking nature, a hypothetical disclaimer, percentile outputs, and a paid-plan restriction not present in annotations. It does not say whether the call is long-running/asynchronous for a 10-year horizon, which is a meaningful gap for a Monte Carlo job.

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 action ('Runs a Monte Carlo of 500 paths'), then outputs, then caveats, then routing. The single long sentence packing simulation size, horizons, and outputs is dense but readable; no filler sentences. Slight cost from parenthetical branding ('the AI Scenario Simulation of acubic.ai'), which is not actionable for an agent.

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 description needn't spell out return values, yet it summarizes the percentile structure anyway. For a read-only simulation tool this covers purpose, inputs' meaning at a high level, entitlement, and the key alternative. Missing only runtime/async expectations and the precondition of an existing completed backtest.

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 75% and the horizon enum is already documented in the schema, so restating '1, 3, 5 or 10 years' adds little. Neither 'locale' nor 'response_format' (concise vs detailed) is explained in the description, so no extra semantic guidance beyond structured fields.

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+resource pair ('Runs a Monte Carlo... for one saved strategy') and quantifies scope (500 paths, 1/3/5/10 years). It also names the sibling it is not — 'For past results use acubic_get_backtest' — so an agent can distinguish projection from backtesting 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 Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly routes past-looking queries to acubic_get_backtest, giving a clear use/when-not boundary. It also implies a prerequisite by saying the projection runs 'from its walk-forward backtest', and flags entitlement ('Paid plans only'). What is missing is an explicit statement of the failure mode when no completed backtest exists for the strategy.

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