Skip to main content
Glama

Economic Release Calendar

GetEconomicCalendar
Read-only

Get the economic release calendar — scheduled (upcoming) and recent publication dates of US and Canadian macro data releases, each row naming its market, with the FRED series each release updates and an importance tier per release (High = the tier-1 scheduled market movers: CPI, PPI, Employment Situation, GDP, PCE, retail sales; Medium = other genuine scheduled prints; Low = daily rate/market levels like SOFR or VIX). FOMC meetings are NOT included — FRED's release feed has no real FOMC meeting dates; use the Federal Reserve's published meeting calendar for those. Defaults to the next 30 days. When a window holds more rows than maxResults, the lower tiers are left out first (the answer says how many), so the scheduled prints are never cut for daily rows. Use minImportance=high to see only the market movers, and GetEconomicIndicator to fetch a series' data after it prints.

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

Input Schema

NameRequiredDescriptionDefault
countryNoMarket country code, US or CA (defaults to every market)
endDateNoEnd date in YYYY-MM-DD format (defaults to 30 days after the start date)
startDateNoStart date in YYYY-MM-DD format (defaults to today, UTC)
maxResultsNoMaximum number of release dates to return (default: 100, max: 500, chronological; over the cap, lower importance tiers are left out before any date is cut)
minImportanceNoMinimum importance tier to include: low, medium, or high (defaults to low = everything that fits maxResults, lower tiers left out first)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / maxResults / description
      Previous value: -"Maximum number of release dates to return (default: 100, max: 500, chronological)"New value: +"Maximum number of release dates to return (default: 100, max: 500, chronological; over the cap, lower importance tiers are left out before any date is cut)"
    • changedInput schema / properties / minImportance / description
      Previous value: -"Minimum importance tier to include: low, medium, or high (defaults to low = everything)"New value: +"Minimum importance tier to include: low, medium, or high (defaults to low = everything that fits maxResults, lower tiers left out first)"
  2. Changed1 schema field changed
    • addedInput schema / properties / country
      Added value: +{
      +  "default": null,
      +  "description": "Market country code, US or CA (defaults to every market)",
      +  "type": "string"
      +}
  3. First observed

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, openWorldHint=false, so the safety profile is covered. The description still adds real behavior the annotations cannot: the 30-day default window and the truncation policy that drops lower importance tiers first while reporting the omitted count. It stops short of discussing freshness, caching, or source latency, which keeps it from a 5.

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 and scope, and each clause carries useful content (tier definitions, FOMC exclusion, truncation rule, next-step tool). It is a single dense block, though, and the parenthetical definitions make it longer than strictly necessary for an agent already primed by the schema.

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 no output schema, the description carries the return-shape burden and does so: each row names its market, the FRED series it updates, and an importance tier. Combined with defaults, truncation behavior, and the exclusion note, an agent has enough to call it correctly on the first try.

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

Parameters5/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, but the description adds meaning the schema does not: it defines what High, Medium, and Low actually contain (tier-1 scheduled movers like CPI, PPI, Employment Situation vs. daily rate levels like SOFR/VIX). That tier vocabulary is the key to using minImportance correctly and is not in the schema.

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 (get the economic release calendar of US/Canadian macro releases), and immediately scopes it as scheduled-plus-recent rather than historical. It distinguishes itself from GetEconomicIndicator (which fetches the series data) and from an FOMC meeting calendar, so an agent can pick it out of the sibling list without opening a schema.

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 explicit when/when-not and alternatives: FOMC dates are out of scope with a concrete redirect to the Federal Reserve's published calendar, and GetEconomicIndicator is named for follow-up data pulls. It also tells the agent to set minImportance=high when only market movers are wanted.

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.