Skip to main content
Glama

NS Pros MCP Gateway

nist-standards__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": "nist-standards__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?

No annotations exist, so the description must carry the whole behavioral load, and it does disclose real traits: results are cached with a ≤60s TTL, there is no push/webhook, and freshness is explicitly not guaranteed for beating a release. That is genuinely useful pre-call context. It says nothing about authentication requirements, rate limits, or what a result actually contains, which leaves meaningful gaps for an unannotated tool.

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?

Front-loaded and dense: the JOIN, the positioning caveat, and the caching caveat all appear before any parameter talk, and every clause carries information. The one structural defect is the truncated CATEGORIES sentence, which dangles without a closing parenthesis or a complete list. Otherwise there is no filler.

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 positioning versus speed distinction and the cache TTL cover the ambiguity that matters most for this tool. However, there is no output schema and the description never indicates what a joined result row looks like or how scheduled releases and markets are paired, which is the core thing an agent must reason about. The cut-off category list compounds the incompleteness.

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, making 3 the baseline. The description adds framing for the window ('scheduled releases land in the next N hours') and begins enumerating categories, but that enumeration is cut off mid-word, so it contributes less than it appears to. No syntax or interaction detail (e.g. how categories combines with the window) is added 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?

States a concrete operation: joining an official release calendar (econ data, FOMC, FDA, SEC) against live Polymarket/Kalshi markets over a look-ahead window. That is a specific verb-plus-resource statement an agent can act on. It does not differentiate itself from the many identically-suffixed sibling tools for other data sources, and the sentence trails off at 'CATEGORIES: econ (CPI, Employment Situation/jobs rep', so the purpose statement ends incomplete.

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?

Gives both a positive use case ('see what is coming and what is already priced') and an explicit exclusion ('do not use this to try to beat a release'), which is stronger than most definitions. The 'positioning tool, not a speed product' framing tells the agent exactly which intent this tool serves and which it does not. It stops short of naming a concrete alternative tool for speed-sensitive 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.