Skip to main content
Glama

NS Pros MCP Gateway

nplg-catalog__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": "nplg-catalog__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 at all, the description carries the full behavior burden and does substantial work: it discloses caching (≤60s TTL), the absence of push/webhook delivery, and that it is a positioning rather than latency tool. It does not describe permissions/auth needs, rate limits, or the shape of the join result, which a no-annotation tool ideally would.

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 lead is well front-loaded — the JOIN and its two outputs come first, and the positioning caveat follows. However, the CATEGORIES section is truncated mid-sentence, leaving an incomplete enumeration and dead weight at the end of the definition.

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 no-annotation, no-output-schema tool, the description is only partially complete: it covers caching, delivery model, and intent well, but the categories list terminates mid-word and there is no indication of what the joined result looks like (fields, matching between releases and markets). That gap matters here because the tool's core value is the join, whose output shape is undocumented anywhere.

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 (hours with default 48 and 720 cap, categories with the valid subset) are already fully documented in the schema. The description only echoes 'next N hours' and starts an enumeration of categories that is cut off mid-word ('Employment Situation/jobs rep'), adding little beyond the structured fields.

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 states a concrete operation (a JOIN of the official release calendar against live Polymarket/Kalshi markets) and the two outputs it produces: which scheduled releases land in the next N hours and which live markets resolve on them. It also scopes the calendar sources (econ data, FOMC, FDA decisions, SEC rules), which distinguishes it from generic calendar siblings. It stops short of naming any specific sibling tool to use instead.

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 an explicit use and an explicit non-use: 'do not use this to try to beat a release, use it to see what is coming and what is already priced.' The schema further advises widening the window rather than assuming nothing is scheduled. No alternative tool is named for the speed/latency case, so it falls short of a 5.

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.