QuantGeeks GEX

GEX ladder (VEX on request)

quantgeeks_get_gex_ladder

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). Per-strike gamma exposure (GEX by default; measure 'vex' returns the VEX ladder, vanna exposure), ONE column for ONE expiration: by default the latest minute and 20 strikes each side of spot, as on the QuantGeeks desk. The reply opens with the expiration (same-day or days out) and the key nodes (primary and two majors). Sizes compare only within one expiration (one book); same-day (0DTE) and later expirations are not comparable. Give center (a strike) or from_strike and to_strike to look away from spot, time (HH:MM ET) for another minute, strikes (up to 60) to widen. Net gamma is QuantGeeks GEX (flow-based); net vanna, with measure 'vex', is VEX; both exact, a readable string such as +$2.0M or −$10.0M (quote it as written) with dollars beside it. For nodes over several sessions use quantgeeks_get_node_history; for forward expirations side by side, 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_gex_ladder"
  }
}

Input Schema

Name	Required	Description
`date`	No	Session date, YYYY-MM-DD (US Eastern). Default: the most recent regular session.
`time`	No	Time of day HH:MM US Eastern. Default: the latest available minute.
`range`	No	Alias of strikes.
`center`	No	Center the window on this strike instead of spot (e.g. 6550).
`symbol`	Yes	Ticker, e.g. SPX (maps to its 0DTE option root SPXW), SPY, QQQ, VIX.
`measure`	No	'gex' (default): QuantGeeks GEX (gamma exposure); 'vex': VEX (vanna exposure). Every number and node in the answer is in the measure it says.
`strikes`	No	Strikes on each side of spot (default 20, at most 60).
`to_strike`	No	Highest strike of a range to show.
`expiration`	No	Option expiration YYYY-MM-DD. Default: the nearest.
`from_strike`	No	Lowest strike of a range to show (with to_strike).

Output Schema

Name	Required	Description	Default
`dte`	No
`date`	Yes
`spot`	Yes
`time`	Yes
`as_of`	Yes
`units`	Yes
`access`	Yes
`notice`	Yes
`source`	Yes
`symbol`	Yes
`account`	No
`measure`	No
`preview`	Yes
`strikes`	Yes
`pro_plan`	No
`key_nodes`	Yes
`truncated`	No
`expiration`	Yes
`window_note`	No
`truncated_more`	No
`expiration_kind`	No
`expiration_note`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 15, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Goes well beyond the readOnly/idempotent/non-destructive annotations by disclosing the access gate (needs a QuantGeeks plan; calls with no sign-in or a free account will prompt for sign-in or a plan) and the reply shape (opens with the expiration and primary plus two major nodes, values are exact strings like +$2.0M). It also warns that sizes are only comparable within one expiration and that 0DTE versus later expirations are not comparable, which is a genuinely useful analytic constraint. A minor gap remains around pagination and truncation when using very wide strike windows.

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?

The access requirement is front-loaded where an agent will see it first, and the sentence order (access, output shape, comparability caveat, parameter levers, siblings) is logical. Some wording is padded, notably the parenthetical explanations of what the sign-in and plan errors say, which cost space without adding decision-relevant information.

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?

For a ten-parameter read-only analytic tool with an output schema, the description covers access constraints, defaults, output shape, comparability limits, and sibling routing. Nothing an agent needs in order to call it correctly or interpret the result is missing.

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 coverage is 100%, so the schema already documents all ten parameters including the `measure` enum and the `range` alias. The description restates the practical usage of `center`, `from_strike`/`to_strike`, `time`, and `strikes`, but adds little semantic detail beyond what the schema fields say; 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 a specific verb and resource: per-strike gamma exposure (GEX) ladder, with `measure` 'vex' switching to a vanna exposure (VEX) ladder, scoped to ONE column for ONE expiration. It explicitly separates itself from quantgeeks_get_node_history and quantgeeks_get_expiration_map by naming the cases those siblings serve.

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?

Gives explicit when-to-use routing: multi-session nodes go to get_node_history, forward expirations side by side go to get_expiration_map. It also spells out how to move the window (``center``, or ``from_strike``/``to_strike``), change the minute (``time``), or widen (``strikes`` up to 60), and states the default behavior (latest minute, 20 strikes each side of spot).

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?