Skip to main content
Glama

Grok Crypto Quant API

Robust strategy parameter optimiser

optimize_strategy
Read-onlyIdempotent

Find robust strategy params, not lucky ones: tests up to 50 combos on the same survivorship-bias-free backtester, ranks by worst-half (H1/H2) return with neighbourhood smoothing, flags overfitting, and recommends the most stable parameters rather than the best-fit ones. Price: $0.50 USDC per call (x402, Base mainnet). Free pre-check: validate_optimize.

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>",
      "grid": "<grid>"
    },
    "name": "optimize_strategy"
  }
}

Input Schema

NameRequiredDescriptionDefault
endNoYYYY-MM-DD
feeNoFee per side (0.009 = 0.9%)
gridYesparam -> values to try; <= 50 combos total, <= 10 values per param
startNoYYYY-MM-DD
rank_byNorobust
slippageNoSlippage per side
strategyYes
universeNo
initial_capitalNoStarting capital in USD

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Goes well beyond the readOnly/idempotent/non-destructive annotations by disclosing the price ($0.50 USDC per call, x402, Base mainnet), the combo ceiling (up to 50), the ranking method (worst-half H1/H2 return with neighbourhood smoothing), and that it flags overfitting. These are exactly the operational facts an agent needs before spending money on a call.

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 core promise and the robust-vs-lucky differentiator, with pricing isolated in a second sentence. The first sentence is dense and multi-clause, but every clause carries distinct information rather than filler.

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?

For a 9-parameter, nested-object, paid tool with no output schema, the description covers cost, compute bounds, ranking logic, and the overfitting flag — enough to decide whether to call it. It could say more about the shape of the returned recommendation (e.g. what the stable parameters and flags look like), which matters when no output schema exists.

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 67%, so the schema carries much of the burden, but the description adds real meaning by explaining what 'robust' ranking means (worst-half return with neighbourhood smoothing) versus plain best-fit, which clarifies the rank_by choice. It does not touch start/end, fee/slippage, universe mode, or grid structure beyond the existing schema text.

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 ('find robust strategy params') and immediately distinguishes itself from the plain backtest sibling by contrasting robust vs. 'lucky' results and 'best-fit' ranking. An agent can tell this is an optimisation/grid-search tool, not a single backtest, without opening the 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?

Implies the use case (you want parameters that generalise rather than the top-scoring combo) and names the free alternative/pre-check ('validate_optimize'), which is a real routing signal. It stops short of stating explicit exclusions, e.g. when to prefer plain backtest or backtest_sample instead.

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