Skip to main content
Glama

Is it out yet? (release status)

get_release_status
Read-onlyIdempotent

Use this when you need to know whether a scheduled US release (CPI, PPI, payrolls, JOLTS, GDP, PCE, FOMC, retail sales, claims) or an S&P 100/NASDAQ-100 earnings 8-K is out, when it was first seen, and actual vs prior vs revision. Free. License: cleared. Attribution required: Sources: BLS, BEA, U.S. Census Bureau, DOL, Federal Reserve Board, SEC EDGAR. Detection timestamps measured by cev-os. 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_release_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoEnd date (ET) YYYY-MM-DD, default 2 days ahead.
fromNoStart date (ET) YYYY-MM-DD, default 7 days ago.
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
tickerNoS&P 100 / NASDAQ-100 ticker: adds its latest 8-K Item 2.02 (earnings) acceptance time.

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

A4/5.0
Behavior4/5

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

Annotations already cover the read-only/idempotent/open-world profile, and the description adds genuinely non-structured context: cost ('Free'), licensing status, a mandatory attribution string, the fact that detection timestamps come from cev-os, and a BEA non-endorsement disclaimer. It omits any mention of rate limits, freshness guarantees, or pagination, so it is strong but not exhaustive.

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?

The trigger and coverage lead the sentence and the operational payload (first-seen, actual/prior/revision) comes before the legal boilerplate. The attribution and BEA disclaimer are lengthy but appear to be mandatory compliance text rather than filler.

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 carries the return-value burden and does so reasonably: release status, first-seen timestamp, and actual/prior/revision values. Defaults for from/to live in the schema, so nothing critical is missing for correct invocation, though response shape (per-event array? fields?) remains only partially described.

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, but the description adds semantic mapping from market jargon to the 'event' vocabulary ('payrolls' → employment_situation, 'claims' → jobless_claims, 'PCE', 'FOMC') and clarifies that 'ticker' targets the latest 8-K Item 2.02 earnings acceptance. That is real value beyond the schema, though the mapping is informal rather than exact.

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 names a specific check ('whether a scheduled US release ... is out'), enumerates the covered release families and the S&P 100/NASDAQ-100 8-K case, and states what it returns (first-seen time, actual vs prior vs revision). It does not explicitly differentiate itself from the closely related sibling get_macro_calendar, 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 to know whether X is out' is an explicit trigger condition, which is clear usage context. However, there is no when-not guidance and no mention of the obvious alternative (get_macro_calendar for forward-looking schedules, get_earnings_reactions for post-release price moves), leaving the agent to infer the boundary.

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