Skip to main content
Glama

NS Pros MCP Gateway

nsf-awards__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": "nsf-awards__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.9/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 load and does disclose a latency/freshness profile (results cached, ≤ 60s TTL) and the absence of push/webhook delivery. That is exactly the behavioral context an agent needs for a market-timing tool. It does not say anything about rate limits or result size, so it is strong but not exhaustive.

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?

Structure is well front-loaded: the JOIN explanation comes first, then positioning caveats. However the description ends abruptly mid-sentence ('econ (CPI, Employment Situation/jobs rep'), leaving a dangling CATEGORIES section that the agent cannot use and that wastes space.

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 should fully carry the return shape; it gestures at it ('which scheduled releases land in the next N hours and which live markets resolve on them') but never specifies fields or format. The CATEGORIES list, which is the main piece of vocabulary an agent would need to pick category values, is truncated, leaving the definition partly incomplete for a two-parameter join tool.

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% and both parameters are documented there, including the 720-hour cap and the enum values for categories. The description adds only a loose restatement ('next N hours') and the category enumeration it starts to give is cut off mid-word, so it contributes nothing beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Names a specific operation (a JOIN of the official release calendar against live Polymarket/Kalshi markets) and a specific scope (next N hours, which live markets resolve on those releases). That is far more concrete than the sibling naming pattern implies, and an agent can tell exactly what comes back without opening the schema.

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?

Explicitly frames the tool as a positioning tool rather than a speed product and gives a clear prohibition ('do not use this to try to beat a release') alongside the intended use ('see what is coming and what is already priced'). No named alternative tool is offered, so it stops short of the 5 bar.

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.