FirmTape - SPX, ES, NQ, RTY gamma levels, 100+ symbols

Archive coverage

get_coverage

Read-onlyIdempotent

What the free FirmTape SPX archive holds: the first and last finished session, how many sessions, and the NYSE trading days in that span that are MISSING from it (weekdays minus US market holidays; early closes count as trading days), optionally inside a from/to window. Use when: 'is 2024-03-15 in the archive', 'how complete is 2023', 'which days are missing' before a study that needs every session. Not for: the newest days themselves (list_sessions) or any measurement (get_session). Limits: the trading calendar covers 2022 to 2026; missing days are reported, never filled in.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`to`	No	Last day of the window, YYYY-MM-DD (default: the archive's last session)
`from`	No	First day of the window, YYYY-MM-DD (default: the archive's first session)

Output Schema

TableJSON Schema

Name	Required	Description
`window`	Yes	The from/to filter as applied (null when not given)
`missing`	Yes	NYSE trading days in that span the archive does not hold, oldest first
`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.
`calendar`	Yes	Which trading calendar the missing days were computed against
`sessions`	Yes	Sessions the archive holds in the window
`unchecked`	No	Archived sessions outside the calendar's years, so not checked for gaps
`data_as_of`	Yes	The time this answer's data is true as of, ISO 8601 with the ET offset: a finished session's close (13:00 on an early close), the minute a ladder was read at, or the source's own build stamp. Null when the source states none.
`last_session`	Yes	Newest session the archive holds in the window, YYYY-MM-DD
`trading_days`	Yes	NYSE trading days from first_session to last_session, inclusive
`first_session`	Yes	Oldest session the archive holds in the window, YYYY-MM-DD
`server_version`	Yes	Version of the FirmTape MCP server that produced this answer

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 3, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Beyond the readOnly/idempotent annotations, it discloses operationally important behavior: the missing-day computation rule (weekdays minus US market holidays, early closes count), the calendar's 2022-2026 coverage limit, and the guarantee that missing days are reported and never filled. These are substantive traits the annotations cannot convey.

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?

The description is dense but front-loads the resource and return shape before usage and limits. Every clause carries information, though the single packed opening sentence is slightly heavy; structure is good but not maximally scannable.

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?

An output schema exists so return values need no prose, yet the description still frames the exact fields returned and the semantics of 'missing'. Combined with the limits and routing guidance, nothing an agent needs to call this correctly is absent.

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%; both from/to parameters are documented with format, pattern, examples, and defaults in the schema itself. The description only restates that they form an optional window, adding little beyond the structured fields, so the baseline of 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?

The description names a specific resource (the SPX archive's coverage) and precisely enumerates what it returns: first/last finished session, session count, and missing NYSE trading days. It clearly distinguishes itself from list_sessions and get_session, so an agent can identify the tool without opening a schema.

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?

It gives explicit 'Use when' examples ('is 2024-03-15 in the archive', 'which days are missing') and an explicit 'Not for' clause naming the two sibling alternatives (list_sessions, get_session) with the condition that selects them. This is textbook when/when-not/alternatives guidance.

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

All FirmTape - SPX, ES, NQ, RTY gamma levels, 100+ symbols tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?