Skip to main content
Glama

FirmTape - SPX dealer positioning, 100+ symbols

by com.firmtape
OverviewDiscussionsAdmin

Market calendar

get_events
Read-onlyIdempotent

The scheduled US market events for a window of days, from the same calendar the FirmTape terminal draws: FOMC decisions, press conferences and minutes, CPI, payrolls, PCE, PPI, GDP, retail sales, JOLTS, ISM, the Fed Chair's speeches, the Beige Book, 10/20/30-year Treasury auctions, mega-cap earnings, monthly and quarterly expiration and early closes. Each event carries its minute in ET, a link to its source, and, where the archive has measured it, what usually follows, what the dealer book did, and for the releases the forecast, the prior and the actual print. Use when: 'what is on the calendar this week', 'when is the next FOMC', 'is there anything at 14:00 today'. Not for: session measurements (get_session) or levels (get_levels). Limits: US only, 2019 to about a year ahead, at most 31 days per call.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
toNoLast day, YYYY-MM-DD (default from + 6 days; at most 31 days)
fromNoFirst day, YYYY-MM-DD (default today, ET)
impactNoLowest impact to include (default med: high and medium)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
toYesTrading day, YYYY-MM-DD
fromYesTrading day, YYYY-MM-DD
eventsYesScheduled US market events in the window, in date and time order
summaryYesOne sentence carrying this answer's numbers, its trading day and its source, written to be quoted verbatim to a reader rather than paraphrased.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedOutput schema / properties / events / items / properties / book
      Added value: +{
+  "description": "What the dealer book did around this kind of event, from the archive, when measured: the flip, the gamma sign at the start of the window, the walls",
+  "type": "string"
+}
    • addedOutput schema / properties / events / items / properties / prints
      Added value: +{
+  "description": "The release's numbers, when known: label, forecast, prior and (after the print) actual, as the release quotes them",
+  "items": {
+    "properties": {
+      "actual": {
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "forecast": {
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "label": {
+        "type": "string"
+      },
+      "prior": {
+        "type": [
+          "string",
+          "null"
+        ]
+      }
+    },
+    "required": [
+      "label"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}
  2. Added

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds extra behavioral context: US-only, date range 2019 to ~a year ahead, max 31 days per call, and each event's metadata. It does not contradict annotations, and the added limits are valuable.

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 long but well-organized: purpose, event list, usage examples, exclusions, limits. Each section earns its place, though some redundancy with the schema (e.g., 31-day limit) could be trimmed. Front-loading the core purpose is effective.

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 (has_output_schema=true), the description need not detail return values. It covers what the tool does, when to use it, what data is included, and its constraints. Nothing an agent needs to decide whether to call it 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 all three parameters are already documented. The description repeats the 31-day limit (also in the 'to' parameter description) and adds no new parameter-level meaning. Baseline of 3 is appropriate when the schema handles parameter documentation.

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 states a specific verb (get/list) and resource (US market events from the FirmTape calendar), enumerates the event types, and explicitly distinguishes itself from get_session and get_levels. An agent can immediately tell what it does and what it is not.

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 provides explicit 'Use when' examples ('what is on the calendar this week', 'when is the next FOMC') and 'Not for' exclusions naming two sibling tools. This is clear guidance for when to choose 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, 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