Skip to main content
Glama

QuantGeeks GEX

Active levels

quantgeeks_get_active_levels
Read-onlyIdempotent

Without signing in: not available; the call asks the user to sign in. Signed in with a free QuantGeeks account: the full Active Levels rows (read rows included) for SPX, SPY, QQQ, META and AAPL only, as of the latest regime read of the trading day that is at least 60 minutes old; any other symbol: the result says it needs a QuantGeeks plan. With a QuantGeeks plan: live rows, refreshed every minute, for every name the desk supports; read rows included. What the desk's Active Levels widget shows: the strikes that matter right now for one book. For the index books that is the primary node, the two major nodes, the first hour's high and low and spot, each with its distance from price and how often today's tape has touched it; for a stock the same from its own gamma book, plus its ladder anchor. The SPX list also carries the current regime read's gates (the level that must hold), invalidation levels and roles (shelf, magnet, wall, trapdoor, hub). Net gamma is QuantGeeks GEX from the live frame (quote the strings as written). Regime reads cover the index books only; names say so in note.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "symbol": "<symbol>"
    },
    "name": "quantgeeks_get_active_levels"
  }
}

Input Schema

NameRequiredDescriptionDefault
symbolYesTicker, e.g. SPX (maps to its 0DTE option root SPXW), SPY, QQQ, VIX.

Output Schema

NameRequiredDescriptionDefault
slotNo
as_ofYes
unitsYes
accessYes
noticeYes
sourceYes
symbolYes
accountNo
previewYes
pro_planNo
minute_atNo
truncatedNo
account_noteNo
read_scheduleNo
delayed_by_minNo
truncated_moreNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior5/5

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

Goes well beyond the annotations (readOnly/idempotent/non-destructive): it discloses the auth tiers and their consequences (unauthenticated prompt, free-tier symbol and read-row limits, unsupported symbol returning a plan message), plus a real freshness contract — 'as of the latest regime read of the trading day that is at least 60 minutes old' for free versus 'refreshed every minute' on a plan. It also warns that regime reads cover index books only and that names say so in `note`, and instructs quoting GEX strings as written.

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?

Dense and largely front-loaded on access tiers rather than on purpose, so a reader learns what they are gated from before learning what the tool gives them. There is redundancy ('read rows included' appears twice) and some run-on sentences packing tiers, refresh cadence and content into single clauses. Nothing is irrelevant, but the wall-of-text form costs scanability.

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 single-parameter read tool with an output schema, the description covers what an agent needs: auth/plan behavior, symbol scope, staleness policy, per-asset-type content shape, the meaning of nodes/roles/gates, and the caveat that regime reads apply to index books only. The one residual gap — no explicit sibling routing — is a usage issue rather than missing behavior.

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 the `symbol` description already covers the SPX→SPXW mapping, so the baseline is 3. The description adds meaning the schema lacks: which symbols are actually permitted on the free tier and what happens with 'any other symbol' (a plan-required result). It stops short of saying whether unlisted-but-supported tickers differ in behavior, but the tier/symbol interaction is genuine added semantics.

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 the resource concretely: 'the strikes that matter right now for one book', enumerating node types (primary node, two major nodes, first-hour high/low, spot) and the SPX extras (regime gates, invalidation, roles). An agent knows this returns level data rather than a raw ladder or price series. However, it never names or contrasts any sibling (e.g. get_gex_ladder, get_node_history, get_readings), so differentiation is implied by content 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?

Usage context is only implied by the access-tier narration: it is the tool for levels on a given symbol. There is no explicit 'use this when' or 'prefer X instead' guidance, and no statement of prerequisites beyond sign-in/plan status. The free-tier symbol restriction (SPX, SPY, QQQ, META, AAPL) is useful routing info but is framing, not when-to-use guidance.

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