Skip to main content
Glama

SquawkFlow Market Structure

Gamma exposure by strike and expiration: the gamma grid

get_gamma_heatmap
Read-onlyIdempotent

Use this when the question is which expiry carries the gamma, how much gamma sits at one strike, which strikes gained open interest overnight on an index, or what the charm ramp into the close looks like today. The gamma heatmap, also called the gamma grid or the gamma surface: dealer gamma broken out by strike AND expiration rather than summed across expiries, in net dollar gamma per 1% move with calls positive and puts negative, plus where same-day (0DTE) trading is concentrated. It also returns the second-order book: vanna and charm exposure, with the charm ramp walked at half-hour marks across one cash session and integrated, so the dealer index delta the clock removes between now and the close is a dollar figure rather than an inference. An aggregate cannot tell 500M in one expiration from 500M spread over several, which is the question this answers. Coverage: SPX, SPY and QQQ only. Served from a five minute cache. Not for: the headline levels alone (get_gex_levels); the sector ETFs (get_gamma_matrix); the full per-strike open interest change or any symbol outside these three (get_oi_change). Limits: the rendered grid shows the nearest six expirations while row totals cover every expiration. Charm and vanna are model outputs, not measurements, and they are quoted in dollars of index delta rather than dollars of gamma, so they are not comparable to any gamma total. Every mark on the charm ramp holds spot and implied volatility at the capture and moves only the clock, which makes it a projection of this book rather than a statement about what happens next. The exposure block is best effort: when it is absent it prints the reason code the endpoint gave. A symbol outside the coverage list returns the SPX grid with a note saying so, not an error.

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

Input Schema

NameRequiredDescriptionDefault
symbolNoSPX, SPY or QQQ, defaulting to SPX, which has the deepest chain and the richest grid. Any other symbol returns the SPX grid plus a coverage note.

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
    • 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"
      +}
  6. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare read-only/idempotent/non-destructive, and the description adds substantial context on top: a five-minute cache, SPX/SPY/QQQ-only coverage, graceful fallback (out-of-coverage symbol returns the SPX grid with a note, not an error), best-effort exposure block printing reason codes, and the caveat that vanna/charm are model outputs in dollars of index delta, not comparable to gamma totals. The remaining gap is that the charm-ramp integration methodology is described in more prose than an agent strictly needs, but nothing behavioral is hidden.

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

Conciseness3/5

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

It is front-loaded with use cases and exclusions, which is good, but it is a dense unbroken block of prose with some rationale that does not change agent behavior (the 'an aggregate cannot tell 500M in one expiration from 500M spread over several' justification). The limits, coverage, and caveats could be tightened considerably without losing signal.

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 one-parameter analytical tool with an output schema, this covers everything an agent needs: what the grid contains, units and sign convention (net dollar gamma per 1% move, calls positive/puts negative), coverage universe, cache freshness, rendering-vs-totals discrepancy, and fallback behavior. Return-value explanation is appropriately delegated to the output schema.

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?

With one parameter at 100% schema coverage, the schema already carries the default and enum values. The description nevertheless adds meaning beyond it by spelling out the fallback semantics — any other symbol returns the SPX grid plus a coverage note rather than an error — which the schema only partially mirrors.

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 a specific resource and decomposition — dealer gamma broken out by strike AND expiration rather than summed — plus the second-order vanna/charm book. It explicitly contrasts with get_gex_levels, get_gamma_matrix, and get_oi_change, so an agent can tell it apart from every sibling 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?

It opens with concrete triggering questions (which expiry carries the gamma, which strikes gained OI overnight, what the charm ramp looks like) and closes with an explicit 'Not for:' list naming the alternative tool for each excluded case. When-to-use, when-not-to-use, and alternatives are all stated.

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