Skip to main content
Glama

GammaRips Options Intelligence

Candidate Pool

get_pool
Read-onlyIdempotent
The GammaRips candidate pool for a scan date. One tool, four `view`s:

  * view="enriched" (DEFAULT) — the AI-enriched pool: news, technicals,
    catalyst, the recommended contract (an OTM call chosen on contract
    liquidity), and the 60-day momentum feature `mom_60`. Funnel for
    scan_date >= 2026-08-24 (liquid-universe era): the 100 most liquid
    optionable names, BULLISH only, one call each, roughly 40-50 rows.
    Liquidity decides membership, not unusual activity; the $500K UOA
    floor is retired and `overnight_score>=1` is a cosmetic floor.
    Earlier scan dates come from the prior UOA-gated funnel (UOA>$500K,
    top-50 BULLISH); the two eras are not one population.
    This is the daily candidate set your agent reasons over to its OWN
    contract (see get_playbook("run-your-own-tournament")). Served from a
    leakage-safe view (forward-outcome columns physically stripped);
    `summary=True` gives ~21 decision columns, `fields=[...]` a strict
    projection, `summary=False` full rows, `offset` pages.
  * view="raw" — the wide overnight scan BEFORE the pool cut (the ranked
    liquid universe for scan_date >= 2026-08-24; the market-wide
    unusual-activity scan for earlier dates). Honors `direction`,
    `min_score`, `ticker`, `limit`.
  * view="features" — point-in-time FEATURE VECTORS from the leakage-safe
    allowlist view `enriched_features_v1` (identity + features + cohort
    metadata only; no outcome/label/telemetry column can appear). The
    quantitative substrate for joining against query_outcomes. Lags the
    live pool by ~1-2 trading days.
  * view="preview" — a 3-contract public sample teaser for the most recent
    scan (3 sample contracts, total pool count that passed today's filter,
    `gated=True`, and an `upgrade_notice` with a link to
    https://gammarips.com/pricing).

TIER: view="preview" is FREE (no key, 3-contract sample). The enriched /
raw / features views are the paid product — they require an active Pro
subscription ($29/mo); an anon/free call to them returns
`subscription_required` (get_pool(view='preview') is named as the free
entry point).

Liquidity caveat (all views): `recommended_oi`/`recommended_volume` are
scan-time snapshots, not live values; `recommended_spread_pct` is
permanently NULL on the current data plan — re-check with get_liquidity.

Args:
    view: "enriched" (default) | "raw" | "features" | "preview".
    scan_date: YYYY-MM-DD (default: latest available scan for the view).
    direction: "bull"/"bear" prefix filter (enriched / raw).
    ticker: exact ticker filter (enriched / raw / features).
    min_score: overnight_score floor (raw view only; clamped 0-10).
    limit: max rows (enriched/raw clamp 1-50, features 1-100, preview 1-3).
    summary: enriched only — True=compact columns, False=full rows.
    fields: enriched only — explicit strict column projection.
    offset: enriched only — pagination offset.

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

Input Schema

NameRequiredDescriptionDefault
viewNoenriched
limitNo
fieldsNo
offsetNo
tickerNo
summaryNo
directionNo
min_scoreNo
scan_dateNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.9/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive/closed-world, and the description still adds substantial behavior: subscription gating with a specific `subscription_required` failure, leakage-safe column stripping, the ~1-2 trading-day lag on features, and the caveat that recommended_oi/volume are scan-time snapshots with recommended_spread_pct permanently NULL. It also warns that the pre- and post-2026-08-24 funnels are 'not one population', which is exactly the kind of semantic hazard an agent cannot infer.

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 four-view breakdown, then tier, then caveats, then a compact args list — a sensible order for a 9-parameter multi-mode tool. It is long, and the leakage-safe/no-outcome-columns point is repeated in both the enriched and features bullets, which is mild redundancy rather than filler.

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 9-parameter, four-mode tool with no output schema, the description covers mode selection, defaults, limits, pagination, auth tier, known data defects, and return shape at the level of detail an agent needs (`summary=True` ~21 decision columns, `summary=False` full rows). Nothing needed to invoke it correctly appears to be missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0% and the schema exposes `view` only as a bare string with no enum, so the description carries the full burden — and does: it lists the four legal view values, states defaults (enriched, latest scan), gives per-view clamping ranges (limit 1-50 / 1-100 / 1-3, min_score 0-10), and marks which parameters are scoped to which view. This meaning exists nowhere in the structured fields.

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 the resource (GammaRips candidate pool for a scan date) and then enumerates four distinct modes with specific content for each: enriched (news/technicals/catalyst/recommended contract/mom_60), raw (pre-pool wide scan), features (leakage-safe feature vectors), preview (3-contract sample). It also distinguishes infrastructure details (funnel era, liquidity-based membership) that let an agent tell this apart from get_liquidity, get_signal, or query_outcomes.

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?

Explicit routing is given: enriched is 'the daily candidate set your agent reasons over to its OWN contract', features is 'the quantitative substrate for joining against query_outcomes', preview is 'the free entry point', raw is the pre-cut universe. When-to-use and which-parameter-applies-to-which-view (direction, min_score, ticker, limit, summary, fields, offset) 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.