Skip to main content
Glama

Release Calendar Markets

release_calendar_markets
Read-onlyIdempotent

JOIN of the official release calendar (econ data, the FOMC, FDA decisions, SEC rules) against LIVE Polymarket/Kalshi markets, which scheduled releases land in the next N hours, and which live markets resolve on them. This is a POSITIONING tool, not a speed product: results are cached like every other pack (≤ 60s TTL) and there is no push/webhook, do not use this to try to beat a release, use it to see what is coming and what is already priced. CATEGORIES: econ (CPI, Employment Situation/jobs report, GDP, PCE, PPI, retail sales, housing starts, jobless claims, via fred_release_dates per known release_id, since FRED's own cross-release calendar mostly returns recent actuals, not future dates), fed (the next FOMC meeting's rate decision, via fomc_calendar), fda (PDUFA action dates + FDA advisory-committee meetings, via pdufa_catalysts / fda_adcom_calendar), sec (SEC final rules whose own DATES clause names an effective date in the window, via federal-register recent_rules, usually finds nothing in a short window since SEC rules typically take effect 30-60 days out, which is an accurate answer, not a bug), court (ALWAYS EMPTY today, court-listener has no forward-looking scheduled-hearing calendar, only filing/termination dates, so this category returns zero releases with unsupported:true rather than fabricate one). Omit categories or pass "all" for every category. MATCHING AND ITS HONESTY CONTRACT: every release is returned even when it has ZERO matched markets, a release is never dropped just because nothing on Polymarket or Kalshi resolves on it (most FDA/SEC releases will show markets:[]; that is signal, not a gap). Every matched market carries resolves_on_this_release: "true" (the venue's own close/end date sits within ~36h of the release AND the question passed a subject filter, econ and fed only), "likely" (same subject filter, but the venue closes days away from the release date), or "unclear" (a keyword hit with no date to anchor against, always true for the fda category, which has no ladder structure to check a date against). matched_by names the mechanism (a Kalshi series ticker, a Polymarket search query, or an FDA keyword probe) so a caller can judge the match rather than trust a label. scheduled_at carries both utc and et; econ releases use the standing BLS/Census 8:30am ET convention (FRED's calendar itself has no clock time), FOMC decisions use the 2:00pm ET convention, and FDA/SEC dates are date_only:true (no reliable clock time exists for either). DO NOT treat a matched market as a real arbitrage or a settled fact on its own, a market question sharing tokens with a release name is not proof it settles on that release's own published number. Call resolution_audit / resolution_diff (fleet #1909) on a specific market before sizing anything here. An empty window (zero releases across every requested category) returns the SAME shape as a populated one, release_count:0, releases:[], plus empty_reason:"no_releases_in_window" and a hint telling you to widen, so you never branch on the response shape and never have to guess whether zero means "nothing is scheduled" or "the lookup failed". Econ releases especially cluster on specific dates each month, so a 48h window often straddles a dead stretch.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "hours": 72
    },
    "name": "release_calendar_markets"
  }
}

Input Schema

NameRequiredDescriptionDefault
hoursNoLook-ahead window in hours from now. Default 48. Capped at 720 (30 days), econ/fed releases are dated weeks apart, so a short window is often empty; widen rather than assume nothing is scheduled.
categoriesNoComma or space separated subset of econ|fed|fda|sec|court, or "all" (default). E.g. "econ,fed" or "fda".

Output Schema

NameRequiredDescriptionDefault
hintNoPresent ONLY on a zero-release window: what to change (usually a wider `hours`).
as_ofNo
notesNo
windowNo
releasesNo
categoriesNo
empty_reasonNoPresent ONLY on a zero-release window: "no_releases_in_window". The window was queried and nothing is scheduled, this is an answer, not a failure.
release_countNo
releases_with_matched_marketsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / hours / description
      Previous value: -"Look-ahead window in hours from now. Default 48. Capped at 720 (30 days) — econ/fed releases are dated weeks apart, so a short window is often empty; widen rather than assume nothing is scheduled."New value: +"Look-ahead window in hours from now. Default 48. Capped at 720 (30 days), econ/fed releases are dated weeks apart, so a short window is often empty; widen rather than assume nothing is scheduled."
    • changedOutput schema / properties / empty_reason / description
      Previous value: -"Present ONLY on a zero-release window: \"no_releases_in_window\". The window was queried and nothing is scheduled — this is an answer, not a failure."New value: +"Present ONLY on a zero-release window: \"no_releases_in_window\". The window was queried and nothing is scheduled, this is an answer, not a failure."
  2. Changed2 schema fields changed
    • addedOutput schema / properties / empty_reason
      Added value: +{
      +  "description": "Present ONLY on a zero-release window: \"no_releases_in_window\". The window was queried and nothing is scheduled — this is an answer, not a failure.",
      +  "type": "string"
      +}
    • addedOutput schema / properties / hint
      Added value: +{
      +  "description": "Present ONLY on a zero-release window: what to change (usually a wider `hours`).",
      +  "type": "string"
      +}
  3. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Goes well beyond the annotations: discloses the ≤60s cache TTL, absence of push/webhooks, that court always returns unsupported:true rather than fabricating, that releases with zero markets are retained, the resolves_on_this_release confidence tiers (true/likely/unclear), the matched_by mechanism, and the clock-time conventions per category. It does not state auth or rate-limit requirements, and the dense matching contract, while honest, could be stated more crisply, keeping it below 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.

Conciseness3/5

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

Front-loaded with purpose and genuinely information-dense, but delivered as one very long paragraph with heavy caps emphasis and some repetition — the empty-window behavior and the clustering of econ releases are each effectively stated twice (once in prose, once in the schema). Sectioning or trimming the duplicated caveats would improve scanability without losing content.

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 two-parameter, read-only, open-world tool with an output schema, the description covers everything an agent needs: category semantics, matching confidence, time conventions, the guaranteed response shape on empty windows, and the honesty contract about not treating matches as arbitrage. Nothing material is left to guess.

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 real meaning: it explains why widening `hours` matters (econ/fed releases are dated weeks apart), what "all" means, and critically that the `court` category is always empty with unsupported:true — a caveat that is not in the schema at all. This compensates for the one genuine ambiguity in the enum-free `categories` string.

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?

The opening states a specific verb and resource: a JOIN of the official release calendar (econ, FOMC, FDA, SEC) against live Polymarket/Kalshi markets, returning which releases land in the next N hours and which markets resolve on them. The category enumeration (econ/fed/fda/sec/court) makes the resource boundary explicit, so an agent can tell it apart from sibling tools like polymarket_edges or bet_research 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?

Explicit when-to-use and when-not-to-use framing: "do not use this to try to beat a release, use it to see what is coming and what is already priced," plus an instruction to call resolution_audit/resolution_diff before sizing any position. It also tells the caller how to broaden results (omit categories, widen hours) and warns that a 48h window often straddles a dead stretch.

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.