Skip to main content
Glama

BRAINIAC Technical Analysis Indicators

Backtest a rule-based strategy

technical-analysis_strategy-backtest
Read-onlyIdempotent

Backtest declarative entry and exit rules built from this product's indicators on caller-supplied bars, with next-open fills, fees, slippage, stops, trades, equity curve and metrics. Price $0.05 USDC. POST /api/v1/technical-analysis/strategy-backtest. An unpaid call returns the x402 payment terms and does not run.

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": {
      "bars": "<bars>",
      "entry": "<entry>"
    },
    "name": "technical-analysis_strategy-backtest"
  }
}

Input Schema

NameRequiredDescriptionDefault
barsYesbars, array. Required.
exitNoexit, object. Optional.
sideNoside, string, one of long, short. Required.long
entryYesentry, object. Required.
feePctNofeePct, number, from 0 to 0.5. Required.
slippagePctNoslippagePct, number, from 0 to 0.5. Required.
stopLossPctNostopLossPct, value. Optional.
positionSizeNopositionSize, object. Required.
takeProfitPctNotakeProfitPct, value. Optional.
initialCapitalNoinitialCapital, number. Required.

Output Schema

NameRequiredDescriptionDefault
paramsNoparams. Object.
tradesNotrades. Array.
warmupNowarmup. Object.
metricsNometrics. Object.
sourcesNosources. Array.
equityCurveNoequityCurve. Array.
limitationsNolimitations. Array.

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, so the bar is lower; the description still adds real value by disclosing fill semantics (next-open), the cost model (fees, slippage, stops), the emitted artifacts (trades, equity curve, metrics), the price of $0.05 USDC, and the important failure mode that an unpaid call returns x402 payment terms without running. That last point is genuinely useful behavior an agent would otherwise trip over.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three sentences, front-loaded with purpose, then the simulation semantics, then cost/access. Every clause carries information an agent cannot get from the schema or annotations, and there is no 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?

For a complex, nested-schema tool with an output schema, the description covers everything the agent needs before calling: what is computed, how fills are priced, that fees/slippage/stops apply, what comes back, and that payment is required up front. Return-value shape is rightly left to the output schema.

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 100%, so the baseline is 3; the description earns above that by explaining that bars are caller-supplied and that the entry/exit objects are declarative rules over product indicators, plus that fills occur at next open. It does not map individual knobs like positionSize or stopLossPct to their effect, so it stops short of 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?

The description states a specific verb and resource — backtest declarative entry/exit rules built from this product's indicators on caller-supplied bars — and enumerates the simulation outputs. That distinguishes it cleanly from the sibling indicator-computation tools, which return indicator series rather than a strategy evaluation.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

It implies the use case (evaluate rule-based strategies over your own OHLCV bars) and clarifies that indicators are 'this product's' rather than arbitrary, but it never says when to prefer this over the sibling indicator tools or what inputs are prerequisites beyond 'caller-supplied bars'. Guidance is implied, not explicit.

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