Skip to main content
Glama

US macro release calendar

get_macro_calendar
Read-onlyIdempotent

Use this when you need official US release times (CPI, PPI, payrolls, GDP, PCE, retail sales, JOLTS, trade balance, productivity, claims, FOMC, ISM dates) with actual and prior values once released. Free. License: cleared. Attribution required: Sources: U.S. Bureau of Labor Statistics (incl. BLS Public Data API), U.S. Bureau of Economic Analysis, U.S. Census Bureau, U.S. Department of Labor, Federal Reserve Board. This service uses BEA data but is not endorsed or certified by BEA. BLS.gov cannot vouch for the data or analyses derived from these data after the data have been retrieved from BLS.gov.

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_macro_calendar"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoEnd date (ET), YYYY-MM-DD. Default: today plus 60 days.
fromNoStart date (ET), YYYY-MM-DD. Default: today minus 30 days.
eventNoComma-separated event types: cpi, ppi, employment_situation, jolts, eci, gdp, pce, retail_sales, jobless_claims, fomc_decision, fomc_minutes, ism_manufacturing, ism_services, trade_balance, productivity
limitNoMax events (1-1000, default 500).
statusNoreleased or scheduled

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / event / description
      Previous value: -"Comma-separated event types: cpi, ppi, employment_situation, jolts, eci, gdp, pce, retail_sales, jobless_claims, fomc_decision, fomc_minutes, ism_manufacturing, ism_services"New value: +"Comma-separated event types: cpi, ppi, employment_situation, jolts, eci, gdp, pce, retail_sales, jobless_claims, fomc_decision, fomc_minutes, ism_manufacturing, ism_services, trade_balance, productivity"
  2. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/openWorld, so the safety profile is covered; the description adds useful context beyond that: values appear only "once released" (implying scheduled entries have no actuals yet), the service is free and license-cleared (no auth or key needed). It omits pagination/response-shape detail beyond the 'actual and prior values' hint, keeping it at 4.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The usage condition is correctly front-loaded, but roughly half the text is a licensing/attribution block that does nothing to help an agent select or invoke the tool. That boilerplate may be legally required, but it dilutes the definition as an invocation aid.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description still conveys what comes back (release times, actual and prior values, coverage of major US indicators) and that access is free. Combined with complete schema docs for dates, event filter, limit and status, an agent has enough to call it correctly; only return-format/pagination specifics are 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 five parameters (to, from, event, limit, status) are already documented in-schema; baseline is 3. The description's event list loosely echoes the `event` parameter but uses different vocabulary (e.g. 'payrolls' vs 'employment_situation'), adding no format or default guidance beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The opening sentence states a specific resource (official US release times) and enumerates the covered event families (CPI, PPI, payrolls, GDP, PCE, FOMC, ISM, etc.), which makes the tool's scope unambiguous. It does not explicitly differentiate from siblings like get_release_status or get_macro_regime, so it stops short of a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

"Use this when you need official US release times ... with actual and prior values once released" gives a clear triggering condition. It does not name any alternative tool or state when to prefer get_release_status instead, so there are no explicit exclusions.

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