QuantGeeks GEX

Option structures, zones and whale prints

quantgeeks_get_structures

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). The multi-leg option structures detected in one symbol's flow for a session (type, strikes, expiration, direction, contracts, notional), the price zones they form (with their label and range), and the largest single-leg whale prints (time in US Eastern, strike, expiration, side, contracts, premium). At most 25 per section, largest first (detail 'all' lifts the cap). Give symbol, optional date (default: the newest session with stored data) and kind ('all', 'structures', 'zones' or 'whales'). For node levels use quantgeeks_get_gex_ladder or quantgeeks_get_active_levels.

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_structures"
  }
}

Input Schema

Name	Required	Description
`date`	No	Session date, YYYY-MM-DD (US Eastern). Default: the newest session with stored data (an overnight session counts).
`kind`	No	'all' (default), 'structures', 'zones' or 'whales'.
`detail`	No	'summary' (default): the largest 25 of each section; 'all': every row of each section.
`symbol`	Yes	Ticker, e.g. SPX, SPY, QQQ.

Output Schema

Name	Required	Description	Default
`date`	Yes
`note`	Yes
`as_of`	Yes
`zones`	No
`access`	Yes
`notice`	Yes
`source`	Yes
`symbol`	Yes
`whales`	No
`account`	No
`preview`	Yes
`pro_plan`	No
`times_are`	Yes
`truncated`	No
`structures`	No
`truncated_more`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 15, 2026

TDQS

A4.3/5.0

Behavior5/5

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

Beyond the readOnly/idempotent annotations, the description discloses what an agent cannot infer: the call fails for free or unauthenticated users with a sign-in prompt, results are capped at 25 rows per section ordered largest-first, and `detail` 'all' lifts that cap. It also specifies whale print times are US Eastern and that the default date is the newest stored session including overnight sessions — meaningful behavioral context for a read tool.

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?

Two dense sentences and a routing sentence; the access constraint is front-loaded where an agent will see it first. Some space is spent enumerating return fields and enum values that the output schema and input schema already carry, which is redundant but not harmful.

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?

For a four-parameter read tool with an output schema, the definition covers access requirements, defaults, result caps, time zone, and sibling routing — everything needed to call it correctly. Enumerating the returned fields duplicates the output schema rather than adding to it, which is the main remaining inefficiency.

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 enums and defaults are already documented in the structured fields, and the prose largely restates them ('all', 'structures', 'zones' or 'whales'). The only added meaning is the tie between `detail` 'all' and the 25-row cap, which is close to what the schema already says. Baseline 3 is appropriate.

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 the exact contents returned — multi-leg structures (type, strikes, expiration, direction, contracts, notional), the zones they form, and the largest single-leg whale prints — scoped to one symbol and one session. It also explicitly disclaims a neighboring capability by pointing to quantgeeks_get_gex_ladder and quantgeeks_get_active_levels for node levels, so an agent can separate it from siblings without opening schemas.

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

Usage Guidelines4/5

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

It states the access precondition (requires a paid QuantGeeks plan; free accounts and signed-out calls fail) and gives an explicit routing rule for an adjacent need: 'For node levels use quantgeeks_get_gex_ladder or quantgeeks_get_active_levels.' It does not contrast against quantgeeks_get_option_chain or the other flow tools, so the guidance is clear but not exhaustive.

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?