Skip to main content
Glama

NS Pros MCP Gateway

ntsb-investigations__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": "ntsb-investigations__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?

With no annotations supplied, the description carries the full behavioral burden, and it does disclose meaningful traits: results are cached with a <=60s TTL and there is no push/webhook delivery. That caching and delivery-model disclosure is genuinely useful and not present in the schema. However, it says nothing about result size, pagination, or what a row actually contains (release fields vs market fields), which matters for a join tool.

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 key framing (positioning tool, not a speed product) is front-loaded, and the caching caveat earns its place. But the prose is padded with all-caps emphasis (JOIN, LIVE, POSITIONING, CATEGORIES) and the final section trails off mid-sentence without closing, leaving the definition structurally incomplete rather than tight.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-parameter, no-annotation, no-output-schema tool, the description covers what it returns, when to use it, and its caching latency profile. The truncated tail is the main deficiency, but the schema independently documents both parameters, so an agent could still call it correctly.

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 in detail, including the 720-hour cap and the econ|fed|fda|sec|court subset. The description adds only the 'next N hours' framing and a categories list that is cut off mid-word. Baseline 3 is appropriate when 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 names a specific operation: a JOIN of an official release calendar (econ data, FOMC, FDA decisions, SEC rules) against live Polymarket/Kalshi markets, returning which releases land in the next N hours and which live markets resolve on them. That is a concrete verb-plus-resource statement an agent can act on. It falls short of 5 because the text is visibly truncated mid-sentence in the CATEGORIES enumeration, leaving the full scope of covered categories unstated.

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 explicit when-not guidance: 'do not use this to try to beat a release' and frames the tool as positioning rather than speed, telling the agent to use it 'to see what is coming and what is already priced.' That is a clear usage context with an exclusion. No named alternative tool is offered for the speed/latency use 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.