Skip to main content
Glama

FirmTape - SPX dealer positioning, 100+ symbols

by com.firmtape
OverviewDiscussionsAdmin

Session summary

get_session
Read-onlyIdempotent

Everything FirmTape measured for ONE finished SPX session: OHLC and VWAP, the zero-gamma flip and how often price crossed it, call/put walls, the hold band, net-gamma percentile, ATM IV at the open. Use when: you want a whole day in a single call. Not for: the level set alone (get_levels returns the same day, narrower), how the levels moved across days (get_level_history), or gamma by strike (get_gex_profile). Limits: finished sessions only, one day per call. Measurements only — FirmTape deliberately publishes no buy/sell signals.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dayYesA 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
NameRequiredDescriptionDefault
dayYesTrading day, YYYY-MM-DD
eventsNoThe day's scheduled market events (high and medium impact), each with its minute in ET, its source, the release's prints when known, and, for an event inside the session, what the book did in the 15 minutes after it
replayYesFree minute-by-minute replay of the session on FirmTape
sessionYesSPX price facts for the session
summaryYesOne sentence carrying this answer's numbers, its trading day and its source, written to be quoted verbatim to a reader rather than paraphrased.
dealer_positioningYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedOutput schema / properties / events
      Added value: +{
+  "description": "The day's scheduled market events (high and medium impact), each with its minute in ET, its source, the release's prints when known, and, for an event inside the session, what the book did in the 15 minutes after it",
+  "items": {
+    "properties": {
+      "after": {
+        "description": "spot over the 15 minutes after the event, the flip and the walls before and after, the net gamma sign; only for events inside the session",
+        "type": "string"
+      },
+      "impact": {
+        "type": "string"
+      },
+      "name": {
+        "type": "string"
+      },
+      "prints": {
+        "items": {
+          "properties": {
+            "actual": {
+              "type": [
+                "string",
+                "null"
+              ]
+            },
+            "forecast": {
+              "type": [
+                "string",
+                "null"
+              ]
+            },
+            "label": {
+              "type": "string"
+            },
+            "prior": {
+              "type": [
+                "string",
+                "null"
+              ]
+            }
+          },
+          "type": "object"
+        },
+        "type": "array"
+      },
+      "time": {
+        "description": "HH:MM ET; empty for an all-day item",
+        "type": "string"
+      },
+      "url": {
+        "type": "string"
+      }
+    },
+    "required": [
+      "time",
+      "name",
+      "impact"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}
  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 cover readOnlyHint, openWorldHint, idempotentHint, and destructiveHint, so the safety profile is known. The description adds value beyond annotations by disclosing that only finished sessions are available, that each call returns one day, and that FirmTape publishes measurements rather than buy/sell signals. No contradiction with 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 is front-loaded with the most important information, followed by clear 'Use when' and 'Not for' sections and a final limitation note. Every sentence earns its place, and the structure makes it easy for an agent to parse quickly.

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 one-parameter read-only tool with an output schema, the description is fully complete: it explains what is returned, when to use it, when not to use it, and its limits. The output schema covers return structure, so nothing essential 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 description coverage is 100%, so the schema already documents the day parameter thoroughly with pattern, examples, and error conditions. The description adds context about the 'finished sessions only' limitation and one-day-per-call behavior, but it does not need to repeat parameter details. Baseline 3 is appropriate.

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 first sentence states a specific resource ('ONE finished SPX session') and enumerates exactly what is returned: OHLC, VWAP, zero-gamma flip, walls, hold band, net-gamma percentile, ATM IV. The 'Not for' section names siblings, so an agent can distinguish this from get_levels, get_level_history, and get_gex_profile without opening their schemas.

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?

Explicitly says 'Use when: you want a whole day in a single call' and gives concrete exclusion cases with sibling names: level set alone, multi-day level movement, and gamma by strike. It also states hard limits: finished sessions only and one day per call. This leaves no ambiguity about when to select this tool.

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