Skip to main content
Glama

Grok Crypto Quant API

Crypto strategy backtest

backtest
Read-onlyIdempotent

Backtest crypto strategies on 399 Coinbase coins without survivorship bias. DIY backtests usually use today's coin list, so dead coins vanish and returns are overstated; this rebuilds the universe from each past day's top coins. Breakout, momentum, dip-buy or MA-trend rules on daily data with fees, slippage, H1/H2 split and a luck flag. No data fetching or backtest code on your side. Price: $0.05 USDC per call (x402, Base mainnet). Free pre-check: validate_backtest. Free sample: backtest_sample.

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

Input Schema

NameRequiredDescriptionDefault
endNoYYYY-MM-DD
feeNoFee per side (0.009 = 0.9%)
startNoYYYY-MM-DD
slippageNoSlippage per side
strategyYes
universeNo
include_tradesNo
initial_capitalNoStarting capital in USD

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations declare the safe-read profile, but the description adds what they cannot: a per-call price ($0.05 USDC, x402 on Base mainnet), that no local data fetching or backtest code is needed, and that results include fees, slippage, an H1/H2 split and a luck flag. Missing is any statement of runtime/latency or result size limits for a compute-heavy backtest.

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 value proposition and the survivorship-bias rationale lead, with pricing and free-alternative pointers trailing as short fragments. Slightly dense and marketing-toned ('DIY backtests usually use today's coin list...'), but every sentence conveys usable information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For an 8-parameter tool with a nested discriminator union and no output schema, the description covers purpose, cost and alternatives but not the shape of the result beyond naming an H1/H2 split and luck flag, nor how universe defaults behave. An agent could call it via the sample-first path but would be guessing at what comes back.

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 63%, so the schema documents many fields (universe modes, gate, atr_mult, lookback, risk_per_trade). The description adds the vocabulary of the four strategy types that map onto the discriminated union, plus the fee/slippage framing, but says nothing about universe mode selection, date range, initial_capital or include_trades, leaving the less-documented params unassisted. Baseline 3 is appropriate.

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?

Names a specific verb and resource ('Backtest crypto strategies on 399 Coinbase coins') and immediately states the differentiator: survivorship-bias-free universe rebuilt from each past day's top coins. It also enumerates the four supported rule families (breakout, momentum, dip-buy, MA-trend), so an agent can tell this apart from backtest_sample and optimize_strategy without opening a 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 the agent to two alternatives with their roles: 'Free pre-check: validate_backtest' and 'Free sample: backtest_sample', and states the paid-per-call condition. It does not say when to use optimize_strategy instead, so it falls short of full when/when-not coverage, but the sibling routing is clear.

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