FirmTape - SPX dealer positioning

Level set

get_levels

Read-onlyIdempotent

Only the dealer-positioning level set for one finished SPX session: zero-gamma flip, call resistance, put support, hold band — plus where the session closed relative to them. A strict subset of get_session. Use when: the levels are the whole question and the rest of the session would be noise. Not for: OHLC, flip crossings, net-gamma percentile or ATM IV (get_session); more than one day (get_level_history); gamma by strike (get_gex_profile). Limits: finished sessions only, one day per call.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`day`	Yes	A finished trading day, YYYY-MM-DD. Weekends, holidays and days before coverage return an error — call list_sessions to see which days exist.

Output Schema

TableJSON Schema

Name	Required	Description
`day`	Yes	Trading day, YYYY-MM-DD
`close`	Yes	Session close
`levels`	Yes	Dealer-positioning levels in SPX index points; null when the session did not produce one
`replay`	Yes	Free minute-by-minute replay of the session on FirmTape
`summary`	Yes	One sentence carrying this answer's numbers, its trading day and its source, written to be quoted verbatim to a reader rather than paraphrased.
`close_minus_flip`	Yes	Close minus zero-gamma flip, index points; positive = closed above the flip

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already cover read-only, idempotent, open-world, and non-destructive behavior. The description adds meaningful context beyond annotations: the tool only serves finished sessions, one day per call, and returns a strict subset of get_session. This clarifies data scope and constraints without contradicting annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description opens with the core definition, then gives crisp usage guidance and exclusions, and ends with limits. Every sentence earns its place, and the structure front-loads the most decision-relevant information.

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 an output schema present, return-value explanation is unnecessary. The description covers what the tool returns, how it relates to siblings, when to use it, when not to, and its hard limits. Nothing an agent needs to select and invoke this tool 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%; the schema already fully documents the 'day' parameter with pattern, examples, and error conditions. The description re-emphasizes 'one day per call' and 'finished sessions only' but adds no new semantic information beyond the schema, 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 resource ('dealer-positioning level set for one finished SPX session'), enumerates the exact contents, and explicitly calls itself 'A strict subset of get_session,' distinguishing it from siblings. An agent can immediately tell what this tool returns and how it differs from related tools.

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' and 'Not for' conditions, naming the exact sibling tools for each excluded case (get_session, get_level_history, get_gex_profile). No ambiguity remains about when to select this tool over alternatives.

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

All FirmTape - SPX dealer positioning tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.6/5.0

Disambiguation5/5

Every tool targets a distinct resource and granularity: documents (search/fetch), session enumeration (list_sessions), day-level measurements (get_session/get_levels), intraday shape (get_gex_profile), multi-day trends (get_level_history), and strategy backtesting (options_strategy_test). The descriptions go further than usual, using explicit 'Not for' cross-references so even get_levels vs get_session — a deliberate strict subset — reads unambiguously.

Naming Consistency4/5

The measurement tools follow a clean get_<nouon> convention (get_session, get_levels, get_level_history, get_gex_profile) and list_sessions fits the verb_nouon pattern. fetch and search are bare single-word verbs that break the pattern slightly — fetch_document / search_documents would be more uniform — and options_strategy_test is a compressed compound, but the overall snake_case style and semantic grouping are predictable.

Tool Count5/5

Eight tools is well within the 3-15 sweet spot for a specialized data server. Each tool carries a clearly differentiated job: two document access, one enumeration, four measurement surfaces (single-day full, single-day levels, intraday ladder, multi-day history), and one analysis operation. Nothing feels like filler and nothing essential is missing.

Completeness4/5

The domain is well covered: session discovery (list_sessions), document retrieval (search/fetch), full daily readings (get_session), subset views (get_levels), intraday gamma shape (get_gex_profile), and cross-day movement (get_level_history) — plus a strategy tester. Minor gaps exist, such as no way to compare gamma-ladder shape across multiple days without repeated get_gex_profile calls, but no workflow dead-ends for the stated purpose.

Resources

Need Help?