Skip to main content
Glama

NS Pros MCP Gateway

nvd__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": "nvd__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, the description carries the full burden and does substantial work: it discloses the ≤60s cache TTL, absence of push/webhook, no real-time guarantee, and that results are a join across two live data sources. The only gap is that the CATEGORIES section is cut off mid-word, so the complete category taxonomy is not documented in the description (though it is partially recoverable from the schema enum).

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 opening is well front-loaded with the core identity and the key usage caveat. However, the text is visibly truncated mid-sentence ('...Employment Situation/jobs rep'), leaving an incomplete CATEGORIES enumeration dangling at the end. Heavy capitalization for emphasis ('POSITIONING', 'JOIN', 'LIVE') adds some noise, but the structure is otherwise logical.

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?

There is no output schema, so the description must convey return shape; it does so at a high level (which releases fall in the window and which markets resolve on them) but does not describe the fields, join/match confidence, or what an unmatched release looks like. Combined with the truncated category list, an agent has enough to call the tool but not a full picture of what comes back.

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 `hours` (default 48, capped at 720) and `categories` (comma/space-separated subset with 'all' default) are already fully documented in the schema. The description adds only a loose restatement of 'next N hours' and category examples via the truncated CATEGORIES list. Baseline 3 applies since the schema does the heavy lifting.

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 verb+resource framing: a JOIN of an official release calendar (econ, FOMC, FDA, SEC) against live Polymarket/Kalshi markets. It clearly states the output concept ('which scheduled releases land in the next N hours, and which live markets resolve on them'). It does not differentiate from sibling tools, but those siblings share the same name and appear to be per-provider variants, so the purpose itself is unambiguous.

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 when-not guidance is present: 'do not use this to try to beat a release, use it to see what is coming and what is already priced' — a clear distinction between this positioning use case and latency-driven use. It also explains the caching TTL and lack of push/webhook, which sets expectations. It stops short of naming an alternative tool for speed-sensitive needs.

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.