Skip to main content
Glama

Next-48h catalyst calendar

get_catalysts
Read-onlyIdempotent

Use this when you need to know whether the next hours contain a scheduled high-impact event: US macro releases, FOMC, Treasury auctions, SEC-filed or estimated earnings, and options expiry, each with an impact tier. Free. License: cleared. Attribution required: Sources: BLS, BEA, U.S. Census Bureau, DOL, Federal Reserve Board, U.S. Treasury (TreasuryDirect), SEC EDGAR. This service uses BEA data but is not endorsed or certified by BEA.

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

Input Schema

NameRequiredDescriptionDefault
hoursNoLook-ahead window in hours (1-168, default 48).
kindsNoComma-separated filter: macro, fed, treasury_auction, earnings, options_expiry.
min_tierNoLowest impact tier to include.
include_estimatedNoInclude estimated (not yet SEC-confirmed) earnings dates (default true).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already establish read-only, open-world, idempotent behavior. The description adds useful category scope and impact-tier detail plus licensing/attribution context, but it omits operational behavior like timezone, update cadence, and whether events can be revised, leaving some ambiguity for a calendar tool.

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 use-case sentence is front-loaded and efficient. The remaining 'Free. License: cleared...' attribution/disclaimer block is legal boilerplate that does not help an agent select or invoke the tool, so the description is not fully concise.

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

Completeness3/5

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

For a multi-category calendar with four optional filters and no output schema, the definition explains the event scope and impact tiers but not the returned record shape, time basis, or freshness. Annotations cover safety, but the description leaves operational details thin.

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 coverage is 100%, so the four parameters are already documented. The description's category list loosely maps to kinds and its 'impact tier' phrase maps to min_tier, but it adds 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 description states a concrete purpose: return scheduled high-impact events over a look-ahead window across named categories with impact tiers. This distinguishes it from most siblings by scope, but it does not explicitly contrast with get_macro_calendar or get_earnings_reactions, which overlap on subsets.

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?

It gives a clear trigger: use when the agent needs to know whether the next hours contain a scheduled high-impact event, and it defines coverage. It does not state when not to use it or name alternatives such as get_macro_calendar for macro-only queries.

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