Skip to main content
Glama

Trading Signals Toolkit

Opening-Range-Breakout Backtest

backtest_opening_range_breakout
Read-only

Opening-range-breakout backtest on your intraday bars: trades, win rate, avg R, total R, profit factor, max drawdown, exits, long/short split and recent trades. Read-only, never places orders. Informational only, not investment advice.

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

Input Schema

NameRequiredDescriptionDefault
rrNoTarget in R multiples (default 2)
tzNoIANA timezone for sessions (default America/New_York)
barsYesOHLCV bars, oldest first: {t (ISO-8601 or epoch s/ms), o, h, l, c, v} or [t,o,h,l,c,v]. Max 5000.
stopNo
minutesNoOpening range minutes (default 15)
directionNo
sessionEndNo
costPerTradeNoCost in points per trade
sessionStartNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, and the description's 'Read-only, never places orders' largely restates that. It does add value by disclosing the result payload (trades, win rate, avg R, profit factor, max drawdown, exits, long/short split, recent trades), which matters because there is no output schema, but it says nothing about determinism, defaults, or how costs/sessions affect results.

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 action and the metric list in one sentence, with short safety caveats after. The metric enumeration is long but earns its place given no output schema; the 'not investment advice' clause is padding but brief.

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 a computation tool with no output schema, describing the returned metrics is the key contribution and it is done reasonably well. However, with nine parameters at 56% coverage and no explanation of session/timezone handling or the stop and direction enums, an agent cannot confidently construct a correct call from the description alone.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is only 56%; 'stop', 'direction', 'sessionStart' and 'sessionEnd' have no schema descriptions, and the description mentions none of the nine parameters. It therefore does not compensate for the gaps — an agent must guess what 'stop: opposite|mid' or the session fields mean.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb+resource ('Opening-range-breakout backtest on your intraday bars') and enumerates the outputs it produces, so an agent knows exactly what it computes. It does not explicitly distinguish itself from the sibling 'opening_range' tool, which likely produces the range levels rather than a backtest, so it stops short of a 5.

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

Usage Guidelines2/5

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

There is no statement of when to use this versus alternatives such as 'opening_range' or 'vwap_bands', no prerequisites (e.g. minimum bar count, ordered bars), and no exclusions. Usage is only implied by 'on your intraday bars'.

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