Skip to main content
Glama

SquawkFlow Market Structure

Gamma exposure (GEX) levels: call wall, put wall, gamma flip

get_gex_levels
Read-onlyIdempotent

Use this when the question is what the SPX, SPY or QQQ levels are today: where the call wall, the put wall, the zero gamma flip or the Swing Line sits right now, or whether an index is in a positive or negative gamma regime. Also called GEX, gamma exposure or dealer gamma positioning. Returns spot, net GEX, the regime, pin strikes and the options-implied session range (the expected move), each with the time the snapshot was captured, and a dated day change row (last price, prior close, change, percent change and its as-of time) that answers whether the symbol is up today. Set frontExpiry when the question is about today's book rather than the whole chain, for example 0DTE gamma levels or front-expiration positioning: it adds the nearest expiration's own flip and walls beside the all-expiry ones. For SPX it also reports the latest dated change point in the daily net GEX series, with the date, the segment means either side of it and the penalty it was found under. Coverage: SPX, SPY and QQQ only. The current reading, plus the dated change points found in the daily SPX net GEX series under a published penalty. No other history. Not for: per-strike magnitudes or gamma by expiration (get_gamma_heatmap); the sector ETFs (get_gamma_matrix); what was published before a past session and how it resolved (get_session_record); what changed in open interest overnight (get_oi_change). Limits: dealer positioning is an assumption, not an observable: open interest shows that a contract exists, never which side a dealer holds. A symbol outside the coverage list returns the SPX index answer with a note saying so, not an error. No wall hold rate is published and any earlier one is withdrawn. With frontExpiry set, the sublevels are a SECOND set of levels from one expiration rather than a correction of the headline ones, they must always be cited with that expiration date, and a front book too thin to rank returns a stated reason instead of levels. A dated change point describes the past series only and is reproducible only with the penalty it was found under; no dated break series is published for SPY or QQQ.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_gex_levels"
  }
}

Input Schema

NameRequiredDescriptionDefault
symbolNoSPX, SPY or QQQ, defaulting to SPX. These three are the whole public allowlist; any other symbol returns the SPX index answer plus a coverage note.
frontExpiryNoAlso report the nearest expiration on its own: its flip, call wall and put wall computed from that expiry's contracts only, which answers whether today's book agrees with the full book. Adds a gamma-grid recompute, so the call takes the chain budget rather than the cheap one. Off by default.

Output Schema

NameRequiredDescriptionDefault
kindYes
pageYes
toolYes
notesYes
staleNo
tableNo
titleYes
usageNo
sourceYes
metricsYes
versionYes
capturedAtNo
source_urlNo
staleSinceNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedOutput schema / properties / page / properties / linkLabel
      Added value: +{
      +  "type": "string"
      +}
  2. Changed1 schema field changed
    • addedOutput schema / properties / source_url
      Added value: +{
      +  "type": "string"
      +}
  3. Changed1 schema field changed
    • addedOutput schema / properties / usage
      Added value: +{
      +  "type": "string"
      +}
  4. Changed1 schema field changed
    • addedOutput schema / properties / page / properties / url
      Added value: +{
      +  "type": "string"
      +}
  5. Changed1 schema field changed
    • addedInput schema / properties / frontExpiry
      Added value: +{
      +  "description": "Also report the nearest expiration on its own: its flip, call wall and put wall computed from that expiry's contracts only, which answers whether today's book agrees with the full book. Adds a gamma-grid recompute, so the call takes the chain budget rather than the cheap one. Off by default.",
      +  "type": "boolean"
      +}
  6. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "$schema": "http://json-schema.org/draft-07/schema#",
      +  "additionalProperties": false,
      +  "properties": {
      +    "capturedAt": {
      +      "type": "string"
      +    },
      +    "kind": {
      +      "const": "squawkflow.panel",
      +      "type": "string"
      +    },
      +    "metrics": {
      +      "items": {
      +        "additionalProperties": false,
      +        "properties": {
      +          "hint": {
      +            "type": "string"
      +          },
      +          "label": {
      +            "type": "string"
      +          },
      +          "value": {
      +            "type": "string"
      +          }
      +        },
      +        "required": [
      +          "label",
      +          "value"
      +        ],
      +        "type": "object"
      +      },
      +      "type": "array"
      +    },
      +    "notes": {
      +      "items": {
      +        "type": "string"
      +      },
      +      "type": "array"
      +    },
      +    "page": {
      +      "additionalProperties": false,
      +      "properties": {
      +        "label": {
      +          "type": "string"
      +        },
      +        "path": {
      +          "type": "string"
      +        }
      +      },
      +      "required": [
      +        "path",
      +        "label"
      +      ],
      +      "type": "object"
      +    },
      +    "source": {
      +      "type": "string"
      +    },
      +    "stale": {
      +      "type": "boolean"
      +    },
      +    "staleSince": {
      +      "type": "string"
      +    },
      +    "table": {
      +      "additionalProperties": false,
      +      "properties": {
      +        "caption": {
      +          "type": "string"
      +        },
      +        "columns": {
      +          "items": {
      +            "type": "string"
      +          },
      +          "type": "array"
      +        },
      +        "rows": {
      +          "items": {
      +            "items": {
      +              "type": "string"
      +            },
      +            "type": "array"
      +          },
      +          "type": "array"
      +        }
      +      },
      +      "required": [
      +        "caption",
      +        "columns",
      +        "rows"
      +      ],
      +      "type": "object"
      +    },
      +    "title": {
      +      "type": "string"
      +    },
      +    "tool": {
      +      "type": "string"
      +    },
      +    "version": {
      +      "const": 1,
      +      "type": "number"
      +    }
      +  },
      +  "required": [
      +    "kind",
      +    "version",
      +    "tool",
      +    "title",
      +    "source",
      +    "metrics",
      +    "notes",
      +    "page"
      +  ],
      +  "type": "object"
      +}
  7. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations only cover the read-only/idempotent safety profile, and the description goes far beyond them: out-of-coverage symbols return the SPX answer with a note rather than an error, frontExpiry sublevels are a second set that must be cited with their expiration date, a too-thin front book returns a stated reason, dealer positioning is an assumption not an observable, and wall hold rate is withdrawn. These are exactly the non-obvious behaviors an agent would otherwise get wrong.

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 use case, then output contents, then the frontExpiry decision, then exclusions and limits — a sensible order. It is dense and runs long as a single block, but nearly every sentence carries a distinct constraint (fallback behavior, citation requirement, withdrawn metric) rather than restating structured fields.

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 two-parameter tool with an output schema, the description covers everything the schema cannot: coverage limits, graceful degradation, the interpretive caveat about dealer positioning, the reproducibility condition on dated change points, and what history is and is not published. No behavior needed to call or read the tool correctly is left unstated.

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

Parameters4/5

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

Schema coverage is 100% and already documents the symbol allowlist and frontExpiry's mechanics, so the baseline is 3. The description still adds meaning: it motivates frontExpiry with example question types (0DTE, front-expiration positioning) and explains that its levels sit beside rather than replace the all-expiry levels, which clarifies how to interpret the flag's output.

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?

Opens with a concrete framing ('what the SPX, SPY or QQQ levels are today') and enumerates the exact outputs — call wall, put wall, zero gamma flip, Swing Line, gamma regime. The title and first sentence together make the resource and scope unmistakable, and it is clearly separable from get_gamma_heatmap and get_gamma_matrix.

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 an explicit trigger ('Use this when the question is...') plus a dedicated 'Not for:' clause that names four alternatives and the specific question each one owns (per-strike magnitudes, sector ETFs, past sessions, overnight OI). The frontExpiry guidance ('when the question is about today's book rather than the whole chain') is a precise use condition, not an inference.

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