Skip to main content
Glama
Sign In

FirmTape - SPX, ES, NQ, RTY gamma levels, 100+ symbols

by com.firmtape
OverviewDiscussionsAdmin

Gamma for another symbol, ES, NQ or RTY

get_symbol_gamma
Read-onlyIdempotent

The latest dealer gamma picture for a symbol OTHER than the SPX archive: index, ETF and stock option chains (for example QQQ, SPY, IWM, NDX, RUT, NVDA, TSLA, GLD, TLT), and the E-mini futures ES, NQ and RTY (MES, MNQ, M2K): ES/NQ/RTY are the SPX/NDX/RUT books moved by the day's basis (future minus index, from put-call parity on the index options; no CME data). Returns spot, the zero-gamma flip, call and put walls and net gamma for the VOLUME book and the OPEN_INTEREST book, the heaviest strikes, a per-expiry table and a trust grade. Use when: the question is about a ticker's gamma exposure, flip or walls right now or at the last close, including ES, NQ or RTY gamma levels. Not for: SPX or ES history or a past date (get_session, get_levels, get_gex_profile, which take symbol ES for past days); anything inside a past session. Limits: latest snapshot only (rebuilt every few minutes in session hours); calls count as dealer-long and puts as dealer-short, which is a convention, not a measurement, and on single stocks it is an approximation (see trust.grade: A and B are indices and ETFs, C and D single stocks). Units: US dollars of dealer delta per 1% move.

Input Schema

NameRequiredDescriptionDefault
symbolYesThe ticker, or ES / MES / NQ / MNQ / RTY / M2K (a dated code such as ESZ26 or RTYZ26 works too). Carried symbols are listed at https://firmtape.com/gex; an unknown ticker returns an error naming that page.
contractNoOptional dated contract for a future symbol. Default is the front contract; in the two weeks before a roll the next one is measured too.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • changedInput schema / properties / contract / examples
      Previous value: -[
-  "ESZ26",
-  "NQH27"
-]New value: +[
+  "ESZ26",
+  "NQH27",
+  "RTYZ26"
+]
    • changedInput schema / properties / contract / pattern
      Previous value: -"^M?(ES|NQ)[FGHJKMNQUVXZ]\\d{1,2}$"New value: +"^(M?ES|M?NQ|RTY|M2K)[FGHJKMNQUVXZ]\\d{1,2}$"
    • changedInput schema / properties / symbol / description
      Previous value: -"The ticker, or ES / MES / NQ / MNQ (a dated code such as ESZ26 works too). Carried symbols are listed at https://firmtape.com/gex; an unknown ticker returns an error naming that page."New value: +"The ticker, or ES / MES / NQ / MNQ / RTY / M2K (a dated code such as ESZ26 or RTYZ26 works too). Carried symbols are listed at https://firmtape.com/gex; an unknown ticker returns an error naming that page."
    • changedInput schema / properties / symbol / examples
      Previous value: -[
-  "QQQ",
-  "NVDA",
-  "ES",
-  "NQ"
-]New value: +[
+  "QQQ",
+  "NVDA",
+  "ES",
+  "NQ",
+  "RTY"
+]
    • changedInput schema / properties / symbol / pattern
      Previous value: -"^\\$?[A-Za-z]{1,5}(\\d{1,2})?$"New value: +"^\\$?([A-Za-z]{1,5}|[Mm]2[Kk][A-Za-z]?)(\\d{1,2})?$"
  2. Changed4 schema fields changed
    • addedInput schema / properties / contract
      Added value: +{
+  "description": "Optional dated contract for a future symbol. Default is the front contract; in the two weeks before a roll the next one is measured too.",
+  "examples": [
+    "ESZ26",
+    "NQH27"
+  ],
+  "pattern": "^M?(ES|NQ)[FGHJKMNQUVXZ]\\d{1,2}$",
+  "type": "string"
+}
    • changedInput schema / properties / symbol / description
      Previous value: -"The ticker. Carried symbols are listed at https://firmtape.com/gex; an unknown ticker returns an error naming that page."New value: +"The ticker, or ES / MES / NQ / MNQ (a dated code such as ESZ26 works too). Carried symbols are listed at https://firmtape.com/gex; an unknown ticker returns an error naming that page."
    • changedInput schema / properties / symbol / examples
      Previous value: -[
-  "QQQ",
-  "NVDA"
-]New value: +[
+  "QQQ",
+  "NVDA",
+  "ES",
+  "NQ"
+]
    • changedInput schema / properties / symbol / pattern
      Previous value: -"^[A-Za-z]{1,5}$"New value: +"^\\$?[A-Za-z]{1,5}(\\d{1,2})?$"
  3. Added

TDQS

A4.6/5.0
Behavior5/5

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

Goes well beyond the readOnly/openWorld/idempotent annotations by disclosing freshness ('latest snapshot only, rebuilt every few minutes in session hours'), the dealer-long/dealer-short convention and its approximation on single stocks, the trust-grade meaning, and the units (USD dealer delta per 1% move). These are exactly the behavioral caveats an agent needs and none are in the structured fields.

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-loads purpose and the critical 'OTHER than SPX' constraint, and every clause carries real information. However it is a dense single block that mixes purpose, symbol lists, basis methodology, return fields, usage, and units, making it heavier than it needs to be for quick scanning.

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?

With no output schema, the description fully compensates by enumerating returned fields (spot, zero-gamma flip, call/put walls, net gamma for VOLUME and OPEN_INTEREST books, heaviest strikes, per-expiry table, trust grade). Combined with symbol scope, freshness, and caveats, an agent has everything needed to call it correctly.

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 description coverage is 100%, so the symbol pattern, examples, and contract semantics are already fully documented in the schema. The description adds futures-context (ES/NQ/RTY, MES/MNQ/M2K) but no syntax or format detail beyond what the schema carries, so the 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+resource ('latest dealer gamma picture') and immediately scopes it as 'for a symbol OTHER than the SPX archive', explicitly distinguishing it from the SPX tool the agent might otherwise assume. It enumerates the supported symbol classes (index/ETF/stock chains, E-mini futures) so the agent knows exactly what universe it covers.

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?

Provides an explicit 'Use when' clause (ticker gamma, flip, walls now or at last close, including ES/NQ/RTY) and a 'Not for' clause naming the exact alternatives (get_session, get_levels, get_gex_profile) and the condition (past date/history) that selects them. This is textbook routing guidance.

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

All FirmTape - SPX, ES, NQ, RTY gamma levels, 100+ symbols toolsInspect
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