Skip to main content
Glama

quantdata

by uk.quantdata

Estimated dealer gamma exposure

quantdata_gamma
Read-only

Estimated dealer gamma exposure (GEX) for a US listed stock or ETF: net and gross GEX, the zero gamma (flip) level and the heaviest strikes. Unlike max pain this is a Black-Scholes ESTIMATE — zero rate, zero dividend, implied volatility solved from end-of-day quotes, and the convention that dealers are long every call and short every put. Keep that framing when reporting it. A null flip is not an error: check flip_status — 'no_sign_change_within_10pct' means net gamma keeps one sign across the whole traded range, which is a state worth reporting. US listed stocks and ETFs only, with a liquid chain: cash-settled index options (SPX, NDX, RUT, VIX) return an error — use SPY, QQQ, IWM instead. Reads the prior session's settled open interest and cannot update intraday whatever the clock says, so report as_of and spot_date with the number.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
symbolYesUS listed stock or ETF ticker, e.g. NVDA or SPY.
by_strikeNoInclude the strike-level gamma profile. Large; only request it when the user wants strike detail.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations include readOnlyHint and openWorldHint. Description adds context: estimation method (Black-Scholes with zero rate/dividend), dealer convention (long calls, short puts), null flip handling, and that it's based on end-of-day quotes. No contradiction with annotations.

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?

Description is lengthy but well-structured, front-loading purpose and key constraints. Each sentence adds necessary detail; could be slightly tighter but no superfluous content.

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?

No output schema provided, but description explains return fields (net/gross GEX, zero gamma flip, heaviest strikes, flip status, as_of, spot_date). Covers behavioral nuances and error handling, making it complete for a complex tool.

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 description coverage is 100%, so baseline is 3. Description adds value: for 'by_strike' it warns it's large and only request when needed; for 'symbol' it reiterates the scope. Substantial extra guidance.

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?

Clearly states it estimates dealer gamma exposure for US listed stocks/ETFs. Distinguishes from siblings like max_pain with a detailed description of the Black-Scholes estimation method.

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?

Explicitly says when to use (US listed stocks/ETFs) and when not (cash-settled index options like SPX, NDX, RUT, VIX), providing alternatives (SPY, QQQ, IWM). Also notes it reads prior session's settled open interest and cannot update intraday.

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

All quantdata toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.7/5.0
Disambiguation5/5

Each tool targets a distinct market data domain: Brooks price action events, dealer gamma, options max pain, API key request, and Weis Wave volume-price structure. Despite some conceptual overlap between options-related tools, their descriptions clearly differentiate calculations and data sources.

Naming Consistency5/5

All five tools follow the exact same `quantdata_<topic>` snake_case pattern, making the naming perfectly uniform and predictable. No mixed conventions or stylistic deviations.

Tool Count5/5

Five tools is a well-scoped set for a specialized quant data server. Each tool serves a clear analytical purpose, and the API key request tool supports access to the four data tools without bloating the surface.

Completeness5/5

The set explicitly covers four market-data categories plus key management, and each tool is fully self-contained for its intended analysis. No obvious dead ends or missing core operations within the stated domain of quantitative market analytics.

Resources