Skip to main content
Glama

NS Pros MCP Gateway

nsi-bg__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": "nsi-bg__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 real work: it discloses the ≤60s cache TTL, the absence of push/webhooks, and the resulting freshness limitation ('POSITIONING tool, not a speed product'). Those are exactly the traits an agent needs before trusting results near a release. It does not describe the shape of the joined output or how unmatched releases/markets appear, which leaves a gap.

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 purpose and the positioning caveat, but the text is dense and cuts off mid-sentence ('CATEGORIES: econ (CPI, Employment Situation/jobs rep'), leaving an incomplete clause that serves no purpose. Signal-heavy sentences about caching sit alongside a dangling fragment, so trimming and completing would materially improve it.

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 covers intent, freshness behavior, and category coverage reasonably well. However, it never explains what a joined result contains (matched pairs? releases with no market? market prices at query time?), which is the central thing an agent must know before calling. The truncated category list further reduces completeness.

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 the schema already explains the `hours` look-ahead window, its 48-hour default, the 720-hour cap, and the `categories` subset syntax. The description reinforces the window concept ('next N hours') but adds no new parameter meaning beyond that. The categories enumeration is actually truncated mid-word in the text, so it contributes nothing the schema does not already say better.

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 concrete verb+resource framing: it joins an official release calendar (econ, FOMC, FDA, SEC) against live Polymarket/Kalshi markets and reports which releases land in the next N hours and which markets resolve on them. That is far more specific than the name alone. It stops short of distinguishing itself from the many sibling `*__release_calendar_markets` tools, though those differ by data source rather than function, so the gap is modest.

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 explicitly states a when-not: 'do not use this to try to beat a release,' and reframes the intended use as seeing 'what is coming and what is already priced.' That is a clear, actionable usage condition rather than implied guidance. It does not name an alternative tool for the speed/event-driven case, which keeps it from 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.