Skip to main content
Glama

NS Pros MCP Gateway

noaa-ndbc__release_calendar_markets

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 rep

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": "noaa-ndbc__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".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does substantial work: it discloses the <=60s cache TTL, the absence of push/webhook, and the resulting latency profile that makes it unsuitable for release-beating. What it omits is equally behavioral: no statement of what the response looks like, how markets are matched to releases, or whether results are paginated or capped by market count.

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 core positioning is front-loaded in the first two clauses, which is good practice. But the prose is dense and comma-spliced, and the CATEGORIES sentence is truncated mid-word, leaving a dangling fragment that reads as an incomplete thought rather than a deliberate summary.

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 tool with no output schema and no annotations, the description should explain the shape of what comes back (release records? market records? a paired join?) and roughly how many results to expect. It covers cache behavior and the timing model well, but the truncated category list and absent return-value sketch leave an agent guessing about result structure.

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 schema already documents 'hours' (default 48, capped 720) and 'categories' (econ|fed|fda|sec|court or 'all'). The description adds only the 'next N hours' look-ahead framing, duplicating what the schema states. The partial CATEGORIES enumeration ('econ (CPI, Employment Situation/jobs rep') is cut off mid-sentence and adds no usable parameter meaning 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 opens with a concrete verb+resource framing: a JOIN of the official release calendar (econ data, FOMC, FDA, SEC rules) against live Polymarket/Kalshi markets, returning which scheduled releases land in the next N hours and which markets resolve on them. That is a precise, non-tautological statement of function. It does not differentiate itself from the many identically-suffixed release_calendar_markets siblings, so it falls 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?

It gives explicit when-not guidance: 'do not use this to try to beat a release, use it to see what is coming and what is already priced,' plus a placement statement ('POSITIONING tool, not a speed product'). That is unusually clear usage scoping. It stops short of 5 because no alternative tool is named for the speed/execution case it explicitly disclaims.

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.