Skip to main content
Glama

NS Pros MCP Gateway

nobel__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": "nobel__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 disclosure burden and does well: it states results are cached with a ≤60s TTL, that there is no push/webhook, and that the tool is read-only in effect ('see what is coming and what is already priced'). It does not mention auth requirements, rate limits, or whether market data is delayed beyond the cache, which keeps it below 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 purpose is front-loaded and the positioning-versus-speed framing is well placed. However the text is cut off mid-sentence in the CATEGORIES block, so the delivered description ends incompletely, and the 'cached like every other pack' aside spends words on background rather than tool behavior.

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-optional-parameter read tool with no output schema, the description covers what the tool does, the behavioral constraints (cache, no webhook), and roughly what comes back ('which scheduled releases land in the next N hours, and which live markets resolve on them'). The truncation of the category enumeration (fda, sec, court are implied by the parenthetical but not listed in the CATEGORIES section) is the main completeness gap.

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%, with both parameters fully documented including the 720-hour cap and the widening advice, so the baseline is 3. The description only echoes 'next N hours' and a partial category list before truncating, adding no meaning beyond the schema.

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 framing ('JOIN of the official release calendar ... against LIVE Polymarket/Kalshi markets') and names the domains covered (econ data, FOMC, FDA decisions, SEC rules), which is far more specific than the name alone. It stops short of a clean single-sentence statement of purpose because the CATEGORIES section is truncated mid-word ('jobs rep'), leaving the enumerated category list 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?

Explicit when/when-not guidance: 'This is a POSITIONING tool, not a speed product ... do not use this to try to beat a release, use it to see what is coming and what is already priced.' That cleanly rules out a latency-sensitive use case. No alternative sibling tool is named, so the agent is not routed elsewhere, 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.