Skip to main content
Glama

Check Edge

tt_check_edge
Read-onlyIdempotent

Has this rule ever actually made money? The FREE screen that kills bad ideas before anyone spends a paid backtest on them.

For a single NSE STOCK on DAILY candles ("buy X when RSI < 30, sell a week later") use tt_backtest_idea instead — it takes stocks, daily bars and hold-N-days exits, and runs the real engine in one more call.

rules is a comma-separated list from tt_scan_instruments, e.g. "price_above_ema20,macd_above_signal". direction is long or short. exit_rule is 'bars:N', 'opposite', or 'session_close'.

DIRECTION AND EXIT ARE REQUIRED AND HAVE NO DEFAULTS, on purpose. An indicator reading says what to WATCH; it does not say which way to trade it or when to get out. If the user has not said, ASK — do not pick. A quietly-invented exit produces a strategy that looks like their idea and behaves nothing like it.

THIS IS NOT A BACKTEST and must never be called one. It trades the SPOT, not options; it applies no brokerage, no statutory charges, no slippage and no sizing. Report the limits string alongside any number. A positive result means only that the idea has EARNED a real backtest — say exactly that, then offer tt_promote_to_strategy, which is the only tool that takes a screened rule set (it builds a validated draft, creates nothing and charges nothing). Do NOT offer tt_backtest_strategy here: it takes a template or a strategy_id, not rules, and it can debit the user's wallet. The order is tt_promote_to_strategy -> tt_create_strategy -> tt_backtest_strategy. Never annualise it, never call it profit, never present it as expected return.

Entries are transitions into the rule set, taken at the NEXT bar's open — never the close that produced the signal. Positions do not overlap.

DATA RULE: the window is lookback_days ENDING 35 days before today (window.ends) for Indian roots — replays of a trading rule there may only use data at least 35 days old (exchange rule); US roots end yesterday. Name that end date; never describe the result as covering recent sessions.

Returns trades, win rate, total, median, payoff, max drawdown, a trade_list of the most recent 25 (with trade_list_scope saying so — the headline figures are over ALL trades and must not be recomputed from that list), plus the wire conditions for the rules so nothing is retyped on the way to a strategy. No auth required.

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": {
      "underlying": "<underlying>"
    },
    "name": "tt_check_edge"
  }
}

Input Schema

NameRequiredDescriptionDefault
rulesNoComma-separated rule names from tt_scan_instruments, e.g. 'price_above_ema20,macd_above_signal'. No default: a call without it is refused, naming it in details.missing_params.
directionNo'long' or 'short'. No default: a call without it is refused, naming it in details.missing_params.
exit_ruleNo'bars:N', 'opposite' or 'session_close'. No default: a call without it is refused, naming it in details.missing_params.
timeframeNo5m
underlyingYes
lookback_daysNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Beyond the readOnly/idempotent annotations it discloses a lot: spot not options, no brokerage/charges/slippage/sizing, entries at the next bar's open, non-overlapping positions, no auth required, and the 35-day data lag for Indian roots. It stops short of stating rate limits or latency, but the safety and semantics picture is unusually thorough for a read-only tool.

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

Conciseness3/5

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

The critical routing and the required-parameter warning are front-loaded and the data rule is clearly marked, but the description runs long with emphatic repetition ('THIS IS NOT A BACKTEST and must never be called one', 'never annualise it, never call it profit, never present it as expected return') that restates the same caution several times.

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?

With no output schema, the description still enumerates the returns (trades, win rate, total, median, payoff, max drawdown, the 25-item trade_list with trade_list_scope, and the wire `conditions`), and it warns not to recompute headline figures from the truncated list. Combined with the data-window caveat and the `limits` string instruction, an agent has what it needs to call and report correctly.

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 50%, and the description compensates well: it explains `rules` as comma-separated names from tt_scan_instruments with an example, gives the `direction` and `exit_rule` value sets, and stresses that direction and exit have no defaults and must be asked for. `lookback_days` is covered by the DATA RULE, but `timeframe` (default 5m) is never mentioned, which is the one real gap.

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 names a specific operation — a free pre-screen of a rule set against historical data that decides whether an idea deserves a real backtest — and explicitly separates it from tt_backtest_idea (single stock, daily bars, hold-N) and tt_backtest_strategy (templates/strategy_id). An agent can route between these without opening any schema.

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?

Explicit when-to-use and when-not-to-use: use tt_backtest_idea for a single NSE stock on daily candles, use this for rule sets, then offer tt_promote_to_strategy, and never offer tt_backtest_strategy here because it can debit the wallet. It even gives the ordering tt_promote_to_strategy -> tt_create_strategy -> tt_backtest_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