Skip to main content
Glama

Kaleidoscope MCP (SEC & financial data)

Macro Calendar (CPI / PCE / EMPLOYMENT / GDP / FOMC — forward macro release dates, PIT-by-construction)

macro_calendar
Read-onlyIdempotent

Forward (or trailing) calendar of major US macro releases — CPI, PCE, EMPLOYMENT (payrolls + unemployment), GDP, FOMC meetings, and EIA weekly energy inventories (WPSR crude Wed + natural-gas storage Thu). The macro counterpart to upcoming_earnings and catalyst_calendar. Use to answer 'what macro prints are coming in the next N days' / 'when was the last FOMC' / 'is CPI in this window.'

PIT semantics: PIT-by-construction. Major-release schedules are published ~1 year in advance, so filtering release_date > as_of IS 'as known then.' Response echoes as_of_effective = as_of (no resolution needed). Reference implementation parity with sec_power_supply_curve and the rest of the as_of-honored catalog.

Inputs (all optional):

  • window_days — forward window in days from as_of (default 30, max 365).

  • as_of — YYYY-MM-DD reference date (default today).

  • categories — restrict to one or more of {CPI, PCE, EMPLOYMENT, GDP, FOMC, EIA_PETROLEUM, EIA_NATGAS}. Omit for all.

  • include_passed — when true, returns a TRAILING window_days window (release_date in [as_of - window_days, as_of]). Default false (forward-only).

  • limit — max rows returned (default 50, max 500).

Coverage: 5,383 release dates, 1947 → 2028. FOMC schedule is static (synthesized from FOMC's published meeting calendar; release_id = -1 on those rows); CPI/PCE/EMPLOYMENT/GDP come from FRED's release calendar. EIA weekly inventories now covered (added 2026-07-11): EIA_PETROLEUM (WPSR, Wed 10:30 ET) + EIA_NATGAS (gas storage, Thu 10:30 ET), 2010 → 2028, generated from EIA's pre-announced weekly schedule with federal-holiday shifts (PIT-by-construction, source='eia_static'). Release DATES only — inventory values live with the stock-data / prices feeds. Rare stacked-holiday weeks are a documented ±1d approximation.

Response shape: list of {category, release_name, release_date, source, release_id} rows sorted by release_date. Plus as_of_effective (= as_of), window (resolved bounds), n_returned.

Verified live (FRED team smoke goldens 2026-06-14): 30d after 2025-01-01 returns EMPLOYMENT 2025-01-10 + CPI 2025-01-15 + FOMC 2025-01-29 + GDP 2025-01-30 + PCE 2025-01-31. CPI as known on 2025-01-01, next 3: 2025-01-15 / 2025-02-12 / 2025-03-12.

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": "macro_calendar"
  }
}

Input Schema

NameRequiredDescriptionDefault
as_ofNoReference date YYYY-MM-DD (default today).
limitNoMax rows returned (default 50, max 500).
categoriesNoRestrict to one or more categories. Omit for all.
window_daysNoForward window in days from as_of (default 30, max 365).
include_passedNoWhen true, returns a TRAILING window [as_of - window_days, as_of] instead of the default forward window (as_of, as_of + window_days]. Default false.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), and the description goes well beyond them: PIT-by-construction semantics, provenance of each category (FRED release calendar vs. synthesized static FOMC with release_id = -1 vs. eia_static), coverage range 1947–2028, and a documented ±1d holiday-shift approximation. It also clarifies that only dates are returned and inventory values live in other feeds, which prevents misuse.

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?

Front-loaded with purpose, then clear bold section headers (PIT semantics, Inputs, Coverage, Response shape), so an agent can skim the first sentence alone. It runs long, and the 'Verified live … smoke goldens' block is developer-facing validation evidence rather than information the calling agent needs, which keeps it from a 5.

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 five-parameter read-only calendar tool with no output schema, the description supplies everything needed: full response shape ({category, release_name, release_date, source, release_id} plus as_of_effective, window, n_returned), sort order, defaults and max bounds, and the PIT caveats. Nothing material is left for the agent to infer.

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%, so the baseline is 3, and much of the Inputs section restates the schema. It earns above baseline by spelling out the resolved interval semantics for include_passed (release_date in [as_of - window_days, as_of] vs. the default forward window) and by tying categories to the exact enum set including the newer EIA categories.

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 and resource (forward/trailing calendar of major US macro releases) and enumerates exactly which categories are covered (CPI, PCE, EMPLOYMENT, GDP, FOMC, EIA_PETROLEUM, EIA_NATGAS). It explicitly positions itself as 'the macro counterpart to `upcoming_earnings` and `catalyst_calendar`', so an agent can distinguish it from calendar-shaped siblings without opening 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?

Gives concrete when-to-use phrasing in the form of example questions ('what macro prints are coming in the next N days', 'when was the last FOMC', 'is CPI in this window'), which also maps the include_passed=true case to the trailing use case. It names the neighboring calendars it complements, so routing is unambiguous.

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