Skip to main content
Glama

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

by com.firmtape
OverviewDiscussionsAdmin

List sessions

list_sessions
Read-onlyIdempotent

List the finished SPX trading sessions in the free FirmTape archive, newest first, with the total count and how far back coverage runs. Every listed day can be fetched with get_session / get_levels and replayed free at FirmTape. Use when: you need to know which days exist, or the size and span of the archive, before asking about one. Not for: any measurement about a day — call get_session with that date instead. Limits: finished sessions only (today's session appears after the close), max 50 days per call.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoHow many days to return (default 10, max 50)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
newestYesTrading days, newest first
summaryYesOne sentence carrying this answer's numbers, its trading day and its source, written to be quoted verbatim to a reader rather than paraphrased.
data_as_ofYesThe 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.
server_versionYesVersion of the FirmTape MCP server that produced this answer
total_sessionsYesHow many finished sessions the free archive holds

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedOutput schema / properties / data_as_of
      Added value: +{
+  "description": "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.",
+  "type": [
+    "string",
+    "null"
+  ]
+}
    • addedOutput schema / properties / server_version
      Added value: +{
+  "description": "Version of the FirmTape MCP server that produced this answer",
+  "type": "string"
+}
    • changedOutput schema / required
      Previous value: -[
-  "summary",
-  "total_sessions",
-  "newest"
-]New value: +[
+  "summary",
+  "total_sessions",
+  "newest",
+  "data_as_of",
+  "server_version"
+]
  2. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, open-world, so the safety profile is covered. The description goes further by disclosing that only finished sessions appear (today's shows after the close) and that each call is capped at 50 days — real behavioral constraints an agent would otherwise have to discover by failing.

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?

Front-loads what the tool returns, then the when/not-for routing, then the limits. Every clause carries distinct information — scope, ordering, routing, freshness, cap — with no filler or repetition.

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-value detail is not required, yet the description still summarizes the key payload (total count, coverage span). Combined with the freshness and cap caveats, an agent has everything needed to call this correctly and interpret the result.

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?

Only one optional parameter and schema description coverage is 100%, so the schema already documents limit, its default of 10 and its max of 50. The description restates the max-50 cap but adds no format or semantics beyond the schema; the baseline of 3 applies when the schema does the heavy lifting.

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 (list) and resource (finished SPX trading sessions in the FirmTape archive), plus ordering (newest first) and what comes back (total count, coverage span). This cleanly separates it from get_session and get_levels, which fetch a single day's data.

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 'Use when' (discovering which days exist, or the archive size/span, before querying a day) and an explicit 'Not for' that routes measurement questions to get_session with a date. The alternative tool is named and the selecting condition is stated, leaving nothing to inference.

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 toolsInspect
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