Skip to main content
Glama

NS Pros MCP Gateway

noaa-ncei__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-ncei__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.6/5.0
Behavior3/5

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

With no annotations, the description must carry the full behavioural burden, and it does disclose real traits: results are cached with a ≤60s TTL and there is no push/webhook. That is valuable beyond what structured fields provide. It says nothing about auth requirements, result caps, or pagination, so several operational traits an agent would want are absent.

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 text is front-loaded with the core JOIN concept and the positioning caveat, then uses an explicit CATEGORIES label for structure. It is dense but earns most of its words. The trailing CATEGORIES sentence is visibly truncated, which undercuts the structure.

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?

The tool is simple (2 optional params, no nested objects, no output schema), and the description covers purpose, latency, and categories. Without an output schema, however, it should at least sketch the shape of the returned match between releases and markets, and the truncated category list leaves the coverage claim incomplete.

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 description coverage is 100%, so both parameters are already documented in the schema, including the 720-hour cap and the enum-like category list. The description adds only the look-ahead framing ('next N hours') and a truncated category enumeration, so baseline 3 applies.

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 uses a specific framing ('JOIN of the official release calendar ... against LIVE Polymarket/Kalshi markets') and states the concrete question it answers: which scheduled releases land in the next N hours and which live markets resolve on them. It also positions itself against an implied alternative behaviour ('a POSITIONING tool, not a speed product'). The final CATEGORIES sentence is cut off mid-word, so the full scope of covered categories is never stated.

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?

Explicit negative guidance is given: 'do not use this to try to beat a release, use it to see what is coming and what is already priced.' That is a genuine when-to-use / when-not-to-use split. It stops short of naming any concrete alternative tool for the speed use case it rules out.

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.