Skip to main content
Glama

SquawkFlow Market Structure

Market calendar: sessions, exchange holidays and the next expiration

get_market_calendar
Read-onlyIdempotent

Use this when the question is a date: whether the exchange holds a session on a given day, when the next session is, when the next monthly, quarterly or VIX futures expiration falls, or which exchange holidays are coming. Returns the published calendar answered as of one date, with the document each entry was read from. Coverage: US equity options expirations, VIX futures settlement dates, the SPX settlement rules as the exchange words them, and the NYSE full-day closure table, each entry read off the exchange document it cites. Answered as of today on the exchange clock, or as of any date you pass. Not for: scheduled economic releases or earnings dates, neither of which this server publishes; market hours, so whether the exchange is open at this moment is not answered here; what SquawkFlow published before a past session (get_session_record); the max pain strike for an expiration (get_max_pain). Limits: no date here is computed from a rule, so a date the exchange documents do not state is reported as not published rather than worked out. Half sessions are not published at all, and a session named here may be one. The closure table covers a stated span of years: a date outside it returns no claim in either direction rather than an assumption that the exchange was open. The next session is the one derived field, taken from that same closure table, and it stops where the table does.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_market_calendar"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateNoISO date the answer is made as of, which is the date "next" is measured from. Omit for today on the exchange clock.

Output Schema

NameRequiredDescriptionDefault
kindYes
pageYes
toolYes
notesYes
staleNo
tableNo
titleYes
usageNo
sourceYes
metricsYes
versionYes
capturedAtNo
source_urlNo
staleSinceNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedOutput schema / properties / page / properties / linkLabel
      Added value: +{
      +  "type": "string"
      +}
  2. Changed1 schema field changed
    • addedOutput schema / properties / source_url
      Added value: +{
      +  "type": "string"
      +}
  3. Changed1 schema field changed
    • addedOutput schema / properties / usage
      Added value: +{
      +  "type": "string"
      +}
  4. Changed1 schema field changed
    • addedOutput schema / properties / page / properties / url
      Added value: +{
      +  "type": "string"
      +}
  5. Added

TDQS

A4.8/5.0
Behavior5/5

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

Annotations only say readOnly/openWorld/idempotent/non-destructive; the description adds substantial behavioral context beyond that: answers are 'as of' a date, each entry cites its source document, no date is rule-computed (undocumented dates return 'not published'), half sessions are omitted entirely, and the closure table covers a bounded year span with silence outside it. These are exactly the caveats an agent needs to interpret results without over-claiming.

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?

It is front-loaded with the trigger condition, then coverage, exclusions, and limits in a sensible order, and most sentences carry distinct information. It is long and has one near-duplication — 'with the document each entry was read from' and 'each entry read off the exchange document it cites' say the same thing — which keeps it just short of top marks.

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, the description need not explain return shapes, and it instead spends its space on scope, sourcing, and the failure modes (unpublished dates, half sessions, out-of-span closure table). For a read-only, one-parameter lookup with real edge cases, nothing material an agent needs before calling is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and the single parameter already documents the ISO pattern and the omit-for-today default. The description still adds meaning by defining the date as the anchor from which 'next' is measured and by tying it to the exchange clock, which clarifies the parameter's role rather than duplicating its format.

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 opening sentence names the concrete question class (whether a session is held, next session, next monthly/quarterly/VIX expiration, upcoming holidays) rather than restating the tool name. It also enumerates the covered data sources (US equity options expirations, VIX settlement, SPX settlement rules, NYSE closure table), so an agent can tell exactly what domain this answers.

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 when-to-use framing ('Use this when the question is a date') is paired with a 'Not for:' block that names three concrete exclusions and routes two of them to siblings (get_session_record, get_max_pain) and one to an out-of-scope topic (economic releases/earnings). The boundary between calendar dates and intraday open/closed status is stated outright.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources