Skip to main content
Glama

NS Pros MCP Gateway

noaa-ncei__updown_venue_compare

The same 15-minute crypto "up or down" window priced on polymarket.com, Polymarket US and Kalshi, side by side, with whether each pair is actually the same contract. Pass asset (btc | eth | sol | xrp | bnb) and window ("current" default, "next", "previous", or the window START as ISO such as 2026-10-27T14:15:00Z, on a 15-minute boundary). Per venue: question, Up bid / ask / mid / last, spread_pp, quote_state, volume WITH ITS UNIT, open interest, liquidity, settlement source, comparison basis, wh

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": {
      "asset": "btc",
      "window": "current",
      "horizon": "15m"
    },
    "name": "noaa-ncei__updown_venue_compare"
  }
}

Input Schema

NameRequiredDescriptionDefault
assetNobtc (default) | eth | sol | xrp | bnb. Coverage differs by venue; a venue that does not list the asset answers not_listed.
windowNo"current" (default), "next", "previous", or the window START as an ISO-8601 timestamp on a 15-minute boundary, e.g. 2026-10-27T14:15:00Z. An unaligned timestamp is refused, not rounded.
horizonNo15m (default and the only value offered).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

No annotations exist, so the prose carries the burden, and it does disclose real behavior: per-venue fields including quote_state, volume with its unit, settlement source and comparison basis, plus the fact that a missing listing surfaces as not_listed rather than an error. It does not mention rate limits, caching/freshness of quotes, or auth, and the final sentence is cut off mid-word, so some behavioral detail is lost.

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?

It is front-loaded with the purpose and dense with useful field enumeration, but the text terminates mid-word ('wh'), leaving a dangling fragment and signalled truncation. The long comma-separated field list also reads as a dump rather than structured guidance.

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?

With no annotations and no output schema, the description must carry the contract, and it does partly by enumerating returned fields and the comparison basis. However the truncation means the return shape is never fully specified, and freshness/quote-state semantics for a time-sensitive 15-minute window go unexplained.

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 coverage is 100% and every parameter already carries a description covering defaults, allowed values and the refusal of unaligned timestamps. The description restates the asset and window contract without adding new syntax or edge-case meaning, so this is the baseline 3.

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 names a concrete verb and resource: pricing the same 15-minute crypto up/down window side by side on polymarket.com, Polymarket US and Kalshi, and flagging whether each pair is actually the same contract. That is specific enough for an agent to know this is a cross-venue equivalence/pricing comparison and not a generic quote lookup.

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

Usage Guidelines3/5

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

It tells the agent how to drive the tool (pass asset and window, with the accepted window values and the 15-minute alignment rule) and implies the use case (checking venue comparability). It gives no explicit when-to-use/when-not guidance or named alternatives, and the per-venue coverage caveat lives in the schema rather than the prose.

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.