Skip to main content
Glama

NS Pros MCP Gateway

noirlab-datalab__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": "noirlab-datalab__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.8/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 disclose the traits that matter most here: caching with a ≤60s TTL, absence of push/webhook delivery, and the deliberate positioning as a slow positioning tool rather than a speed feed. It does not describe the shape of the joined result or any access/pagination constraints, which keeps it off a 5.

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 operational core is front-loaded and wastes nothing, but the text is truncated mid-sentence in the CATEGORIES block, so a section the description itself sets up is left dangling. Heavy capitalization (JOIN, LIVE, POSITIONING, CATEGORIES) aids scanning but the truncation is a structural defect.

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-param, zero-required read tool with full schema coverage and no output schema, the definition covers purpose, timing semantics, latency expectations, and result intent. The one real gap is the severed category list, which an agent may need in order to know the full set of release types it can filter on.

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 the schema already explains the hours window, the 720 cap, and the econ|fed|fda|sec|court category set. The description adds the "next N hours" framing but no new syntax or format detail beyond that, so it sits at the baseline for high-coverage schemas.

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 opening clause names a specific operation (a JOIN of the official release calendar against live Polymarket/Kalshi markets) and the two things it returns: which scheduled releases fall in the next N hours and which live markets resolve on them. That is far more specific than a restated name. It stops short of 5 only because the CATEGORIES enumeration is cut off mid-word ("jobs rep"), leaving the cover scope incomplete.

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?

The definition gives an explicit when-not: do not use this to beat a release, there is no push/webhook and results are cached at ≤60s TTL. It also states the intended when: to see what is coming and what is already priced. It never names a sibling or alternative tool to use instead for latency-sensitive work, so it is clear context without routing.

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.