Skip to main content
Glama

FlashAlpha (Unofficial)

Flashalpha Gex

flashalpha_gex
Read-onlyIdempotent

Get options gamma exposure (GEX) by strike for an underlying, net GEX, gamma flip, and per-strike call/put gamma. Useful for reading dealer positioning and likely support/resistance. Example: flashalpha_gex({ symbol: "SPY", _apiKey: "your-key" })

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "symbol": "SPY",
      "_apiKey": "your-flashalpha-api-key"
    },
    "name": "flashalpha_gex"
  }
}

Input Schema

NameRequiredDescriptionDefault
symbolYesUnderlying ticker symbol, e.g. "SPY", "AAPL", "QQQ"
_apiKeyYesFlashAlpha API key (get one at https://flashalpha.com/pricing)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the safety bar is low. The description adds real value beyond them by naming the return payload (net GEX, gamma flip, per-strike call/put gamma), which matters since there is no output schema. It still omits data freshness, expiry/tenor scope, and rate-limit behavior for an open-world API-backed read.

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 core capability, then use case, then a concrete call example — no filler sentences. The embedded example is somewhat duplicative of the schema's examples list, the only mild waste.

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 two-parameter read tool with no output schema, the description covers what the tool produces and why an agent would call it. The main residual gap is tenor/expiry scope — an agent cannot tell which expirations the per-strike GEX reflects — but overall it is sufficient to invoke 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%, with both parameters fully documented in-schema, so the baseline is 3. The description's inline example restates the schema's own examples without adding new meaning about symbol format or key handling.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Get options gamma exposure (GEX) by strike') and enumerates the concrete outputs: net GEX, gamma flip, per-strike call/put gamma. It does not explicitly contrast itself with the sibling flashalpha_greeks/flashalpha_iv/flashalpha_levels tools, so differentiation is implied by the metric name rather than stated.

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

Usage Guidelines3/5

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

'Useful for reading dealer positioning and likely support/resistance' gives a legitimate use context, but there is no statement of when to prefer this over the Greeks/IV/levels siblings, no prerequisites beyond the key, and no exclusions or limitations. Usage is implied rather than directed.

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.