QuantGeeks GEX

Node history

quantgeeks_get_node_history

Read-onlyIdempotent

Requires a QuantGeeks plan; not available without signing in (the call asks the user to sign in) or with a free account (the call says it needs a plan). How a name's primary and major nodes evolved across a date range, in one call: strike, polarity and size at each session's close (every 'close', default), every N minutes (N of at least 5), or at one time (HH:MM ET) each session. Defaults to the last 5 sessions with data; at most 30 sessions and 50 points. Sizes are GEX (QuantGeeks, flow-based) for the nearest expiration. Reports change: a roll moves the primary to a new strike on the same side of spot, a flip moves it across spot; plus size change, sign pattern and concentration. For one minute's full ladder use quantgeeks_get_gex_ladder; for forward expirations, quantgeeks_get_expiration_map.

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": {
      "symbol": "<symbol>"
    },
    "name": "quantgeeks_get_node_history"
  }
}

Input Schema

Name	Required	Description
`to`	No	Last session date, YYYY-MM-DD (US Eastern). Default: the newest session with stored data (an overnight session counts).
`from`	No	First session date, YYYY-MM-DD (US Eastern). Default: 5 sessions before the last.
`time`	No	HH:MM US Eastern: one point per session at this time (overrides every).
`every`	No	'close' (default): the last minute of each session; or minutes between samples, at least 5.
`symbol`	Yes	Ticker, e.g. SPX (maps to SPXW), SPY, QQQ, GLD.

Output Schema

Name	Required	Description	Default
`hint`	No
`note`	No
`as_of`	Yes
`access`	Yes
`notice`	Yes
`points`	Yes
`source`	Yes
`symbol`	Yes
`account`	No
`measure`	Yes
`preview`	Yes
`summary`	No
`coverage`	No
`pro_plan`	No
`sampling`	No
`truncated`	No
`truncated_more`	No
`expiration_basis`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 15, 2026

TDQS

A4.2/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the description earns credit for adding what annotations cannot: the paid-plan gate, the 5-session default, the 30-session and 50-point caps, and the semantics of roll vs flip and GEX sizing. It does not discuss failure modes beyond the sign-in/plan message or any latency/cost behavior.

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-loads the access precondition, then purpose, then sampling modes, then limits, then alternatives — a logical order with minimal waste. It is dense with parentheticals and would read better split, but no sentence is filler.

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 annotations carrying the safety profile, a full-coverage input schema, and an output schema to explain return values, the description covers everything an agent needs: access gating, scope, sampling options, caps, and sibling routing.

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 from/to/time/every/symbol are already documented, including defaults and the minimum of 5 minutes. The description largely restates those defaults ('every' close default, last 5 sessions, at most 30 sessions and 50 points) rather than adding new meaning; the baseline 3 applies.

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 the specific resource and scope: 'How a name's primary and major nodes evolved across a date range, in one call', and names what it does not do by routing to quantgeeks_get_gex_ladder and quantgeeks_get_expiration_map. An agent can distinguish this from siblings without opening a 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 routing: one-minute full ladder goes to get_gex_ladder, forward expirations go to get_expiration_map, and this tool is for primary/major node evolution over sessions. It also states the plan/sign-in precondition, which determines whether the call is even viable.

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

All QuantGeeks GEX 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?