Regime

Strategy grid lookup

strategy_grid_lookup

Read-onlyIdempotent

Backtest lookup: what one exact version of a strategy actually did. Buy-the-dip and the moving-average cross, every combination of their knobs, computed over nine years of real prices with the exchange's fees charged both ways — sixteen coins, three of which died. Give the coin and the numbers and you get the return, the trades, the worst drawdown, and what buying and holding did over the same window. Read from a file you can download.

Use when someone quotes a specific dip-buying or moving-average rule ("buy 10% dips, take 5%") and you want its real backtest. For leverage use leverage_survival; for a stop on a plain buy-and-hold, stop_loss_check; to judge a win rate you were shown, overfitting_odds.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`coin`	Yes	BTC, ETH, SOL, DOGE, PEPE, SRM… ticker or full pair. Ask with an unknown one and the answer lists the sixteen we hold.
`drop`	No	dip only: how far below its recent high to buy, in %.
`fast`	No	cross only: fast average.
`slow`	No	cross only: slow average.
`stop`	No	dip only: stop loss, in %.
`hours`	No	dip only: give up after this many hours.
`family`	No	dip (buy when it falls) or cross (moving average crossover). Defaults to dip.	dip
`target`	No	dip only: take profit, in %.
`candles`	No	cross only: 1d or 4h.

Output Schema

TableJSON Schema

Name	Required	Description
`ok`	No	false when we do not hold that data. Never a zero standing in for an answer.
`rule`	No	The rule in plain English.
`error`	No	no_data when ok is false.
`reason`	No	Why, in one sentence, and what we do have instead.
`source`	No	The public file these numbers come from.
`trades`	No	How many trades it took.
`return_pct`	No	What it returned, after fees.
`win_rate_pct`	No	Share of winners.
`buy_and_hold_pct`	No	What buying the coin and leaving it alone returned over the same window. A result without this is advertising.
`max_drawdown_pct`	No	Worst peak-to-trough fall.
`versions_in_family`	No	How many versions of this idea exist.
`versions_beating_buy_and_hold`	No	How many of them beat doing nothing. Often zero.

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedOct 2, 2026
- addedInput schema / properties / candles / enum
```
Added value: +[
+  "1d",
+  "4h"
+]
```
- addedInput schema / properties / family / default
```
Added value: +"dip"
```
- addedInput schema / properties / family / enum
```
Added value: +[
+  "dip",
+  "cross"
+]
```
First observedOct 1, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=false, and destructiveHint=false, covering the safety profile. The description adds context beyond annotations: data is computed over nine years of real prices with exchange fees charged both ways, across sixteen coins (three of which died), and results are read from a downloadable file. It also previews return values (return, trades, worst drawdown, buy-and-hold), though an output schema exists.

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?

Purpose is front-loaded in the first sentence. The description is slightly verbose with colorful phrasing ('knobs', 'sixteen coins, three of which died') but each sentence carries relevant information about scope, returns, data source, and routing. It could be tightened, but it remains structured and readable.

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 tool with an output schema and rich annotations, the description covers purpose, data coverage, outputs, and alternatives. It does not detail every parameter or edge case, but the output schema and 100% schema coverage handle those. It is largely complete for correct selection and invocation.

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 description coverage is 100%, so the input schema already documents all nine parameters, including enum values and defaults. The description only broadly references 'the coin and the numbers' and 'every combination of their knobs', adding no syntax or format details beyond the schema. Baseline 3 is appropriate when the schema does the heavy lifting.

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 ('Backtest lookup') and resource: what one exact version of a strategy actually did. Distinguishes from siblings by naming leverage_survival, stop_loss_check, and overfitting_odds for alternative use cases. An agent can immediately tell this is the tool for backtesting a specific dip-buying or moving-average rule.

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

Usage Guidelines5/5

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

Explicitly says when to use: when someone quotes a specific dip-buying or moving-average rule and you want its real backtest. Names three alternatives and the conditions that select them: leverage_survival for leverage, stop_loss_check for a stop on plain buy-and-hold, overfitting_odds to judge a win rate. Nothing is left to inference.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Regime tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?