Skip to main content
Glama

NS Pros MCP Gateway

nj-mvc__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": "nj-mvc__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

A4.3/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are supplied, so the description carries the full burden, and it does substantial work: results are cached with a <=60s TTL and there is no push/webhook. That discloses staleness and delivery semantics that an agent could not infer from the schema. It stops short of describing the response shape or result-count limits, 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded with the JOIN purpose, then positioning caveats, then categories, with almost no filler. It loses a point because the text is truncated mid-sentence at 'CATEGORIES: econ (CPI, Employment Situation/jobs rep', leaving a dangling enumeration that reads as malformed rather than deliberate.

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, zero-required read tool with no annotations and no output schema, the description covers purpose, delivery semantics, and intended use well enough to call it correctly. The truncation removes the explanation of what each category bucket contains, and result shape is only implied, which are the remaining gaps.

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 (hours, categories) already carry detailed schema descriptions including the 720-hour cap and the category enum. The description adds the framing that a short window is often empty because econ/fed releases are dated weeks apart, but that point is also made in the schema. Baseline 3 applies 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.

Purpose5/5

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

The description opens with a precise verb and resource: a JOIN of the official release calendar (econ data, FOMC, FDA, SEC) against live Polymarket/Kalshi markets, returning which releases land in the next N hours and which live markets resolve on them. That is a specific, unambiguous statement of what the tool returns, far beyond a restatement of the name.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It explicitly frames the tool as a positioning tool and names the excluded use case: 'do not use this to try to beat a release, use it to see what is coming and what is already priced.' That is an explicit when-not plus a positive use statement, which is exactly the guidance an agent needs to pick this over a speed/streaming approach.

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.