Skip to main content
Glama

Trading Signals Toolkit

Opening Range

opening_range
Read-only

Opening range (first N minutes) high/low/size for the latest session in your bars, breakout state, first breakout and 1x/2x extension targets. 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": "opening_range"
  }
}

Input Schema

NameRequiredDescriptionDefault
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.
minutesNoOpening range minutes (default 15)
sessionEndNoHH:MM in tz (default 16:00)
sessionStartNoHH:MM in tz (default 09:30)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

The description restates what annotations already declare (read-only, never places orders) and adds a disclaimer plus the 'latest session in your bars' scoping, which is genuinely useful behavior. It does not explain what values 'breakout state' can take, how the range is computed when bars do not cover the full opening window, or what happens with thin data, so the behavioral picture is only partly filled in.

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

Conciseness5/5

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

Three short, front-loaded clauses: what it computes, that it is read-only, and a disclaimer. No filler, and the key output list arrives before the caveats.

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?

With no output schema, the description usefully enumerates the returned fields (range high/low/size, breakout state, first breakout, extension targets), which compensates well. Remaining gaps are the domain of the 'breakout state' values and edge-case behavior with insufficient bars, which keep it short of full completeness.

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 tz, minutes, sessionStart and sessionEnd are already fully documented with defaults, and the description only echoes 'first N minutes'. It adds no syntax or format guidance beyond the schema, which is the expected baseline when the schema carries the burden.

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?

Names the specific computation (opening range high/low/size over the first N minutes of the latest session) and enumerates the derived outputs (breakout state, first breakout, 1x/2x extension targets). It is clearly a read-only analytical calculator over supplied bars, but it never names or contrasts itself with the sibling backtest_opening_range_breakout, which is the nearest confusable tool.

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

Usage Guidelines3/5

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

The phrase 'for the latest session in your bars' implies you must supply your own OHLCV data and get only current-session levels, which hints at usage. There is no explicit when-to-use, when-not-to-use, or pointer to an alternative such as the backtest sibling, so selection between the two remains inferential.

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