Skip to main content
Glama

FirmTape - SPX dealer positioning, 100+ symbols

Screen sessions

screen_sessions
Read-onlyIdempotent

Filter the finished SPX sessions in the FirmTape archive by their closing measurements and count them: regime at the close and at the open, zero-gamma flip crossings, whether the expected-hold band held, direction and size of the move, net-gamma percentile, 0DTE ATM IV at the open, the calendar event, weekday and year. Returns how many sessions match, three shares over them (closed above the flip, band held, mean absolute move) printed next to the same shares over the whole archive, and the matched days. A matched share close to the archive's share is a base rate, not a pattern. Use when: 'how often did FOMC days close in negative gamma', 'the days the band broke with the percentile under 20', 'largest moves on CPI days since 2024'. Not for: one day's numbers (get_session), gamma by strike (get_gex_profile), or testing a rule with out-of-sample statistics (the Lab). Limits: counts over finished sessions' closing measurements only, no per-strike data; at most 50 sessions listed per call. Counts, not investment advice.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ivNo0DTE ATM implied vol at the open: under 10%, 10-15%, 15-20%, 20% and above
dirNoDirection of the open-to-close move
dowNoDay of the week
bandNoWhether the expected-hold band held all session
gpctNoNet-gamma percentile at the close: under 20, 20 to 50, 50 to 80, 80 and above
moveNoSize of the open-to-close move: under 0.5%, 0.5% or more, 1% or more, 2% or more
openNoRegime at the open: pos = opened above the flip, neg = below
sortNoOrder of the sessions list: newest (default), oldest, move (largest absolute move first), gpct (highest percentile first)
yearNoCalendar year, e.g. 2025; a year outside the archive is dropped
crossNoFlip crossings in the session: 0 = none, 1 = exactly one, 2 = two or more
eventNoEvent the day carried: fomc (decision days), cpi, nfp (payrolls), pce, ppi, gdp, retail (retail sales), jolts, ism, claims, auctions (Treasury), fed (speeches, Beige Book), opex (expiration), vix (VIX settlement), umich, confidence, eia, halts (halt in a top name), housing (housing and durables), refunding, rebalances (index), none (no event of these kinds)
limitNoHow many matched sessions to list (default 20, max 50); the counts always cover every match
regimeNoRegime at the close: pos = closed above the zero-gamma flip, neg = below

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesThe /screener page that shows the same result to a person
labelYesThe filters in words
sharesYesThe same three shares over the matched sessions and over the whole archive; a matched share close to the archive's is a base rate, not a pattern
sourceNo
filtersNoThe filters the screener accepted; a value outside the vocabulary is dropped, not an error
matchedYesSessions matching every filter
summaryYesOne sentence carrying this answer's numbers, its trading day and its source, written to be quoted verbatim to a reader rather than paraphrased.
archivedYesFinished sessions in the archive
screenedYesSessions whose closing measurements were available to screen
sessionsYesMatched sessions in the requested order (default newest first), at most `limit`
truncatedYesTrue when more sessions matched than `sessions` carries
question_urlNoWhen the filters are one of the screener's common questions, that question's own page (e.g. /screener/negative-gamma-closes), the address to cite

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior5/5

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

With annotations already declaring readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, the bar is lower, yet the description adds substantial behavioral value beyond them: the matched-vs-archive comparison semantics, the critical base-rate caveat ('A matched share close to the archive's share is a base rate, not a pattern'), the closing-measurements-only scope, the per-call 50-session cap, and the disclaiming close. No contradiction with annotations (a read-only screening operation).

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?

Dense but efficient: the core purpose and filter dimensions are front-loaded, followed by return structure, the base-rate interpretation caveat, routing guidance, and scope limits. Every sentence earns its place for a 13-parameter tool, though it is verbose enough that it cannot reach a 5 on conciseness.

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?

Given the tool's complexity (13 params, screening plus archive-comparison semantics), the description is complete. An output schema exists to document return values, annotations carry the safety profile, and the description covers purpose, routing, interpretation caveat, scope limits, and disclaimers. Nothing an agent needs to select and invoke it correctly is missing.

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 coverage is 100% with all 13 parameters documented (including enum meanings and the limit semantics), so the schema carries the full weight. The description adds contextual framing — mapping which dimensions are filterable — but introduces no new parameter syntax or value semantics beyond the schema. Baseline 3 is correct.

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 (filter and count) and resource (finished SPX sessions in the FirmTape archive), then enumerates the exact filter dimensions (regime, crossings, band, direction, move size, gamma percentile, IV, event, weekday, year). It names what it is NOT for (get_session, get_gex_profile, the Lab), making it fully distinguishable from siblings.

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 explicit 'Use when' examples ('how often did FOMC days close in negative gamma', 'largest moves on CPI days since 2024') and explicit 'Not for' exclusions that cite alternative tools (get_session for one day's numbers, get_gex_profile for gamma by strike, the Lab for out-of-sample testing). No inference left to the agent.

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