Skip to main content
Glama

NS Pros MCP Gateway

noaa-ndbc__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-ndbc__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.5/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does substantial work: it discloses per-venue field coverage (question, Up bid/ask/mid/last, spread_pp, quote_state, volume with its unit, open interest, liquidity, settlement source, comparison basis), notes that venues may answer 'not_listed' for unsupported assets, and states that an unaligned timestamp is refused rather than rounded. It also flags that the output adjudicates whether each pair is the same contract, which is the key behavioral nuance. Missing auth, rate-limit, and pagination context keeps it below 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 core purpose is front-loaded in one dense, information-rich sentence, and little is wasted on filler. But the description terminates mid-word ('wh'), leaving an incomplete clause that dents both polish and usability. It is otherwise compact for the amount of payload detail conveyed.

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?

There is no output schema, so the description must explain return values, and it attempts this with a detailed per-venue field list. That list is truncated before completion, so an agent cannot fully anticipate the response shape or the comparison-basis output. Combined with the absence of annotations, the definition is serviceable but not complete for a multi-venue comparison tool.

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 documents asset, window, and horizon with examples, so the description's parameter guidance largely restates finite detail. It adds marginal value by reinforcing the 15-minute boundary constraint and the venue-specific coverage caveat. Baseline 3 is appropriate when the schema is doing 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 opening sentence names a specific resource and verb: the same 15-minute crypto 'up or down' window priced on polymarket.com, Polymarket US and Kalshi, side by side. That is far more than a restatement of the name and tells an agent exactly what question the tool answers, including the cross-venue framing. The only deduction is that the closing clause describing the per-venue payload is cut off mid-word ('wh'), so the full scope of the response is never cleanly stated.

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?

Usage is described operationally ('Pass asset ... and window ...') and the allowed window values are enumerated, so an agent knows how to invoke it. However, there is no explicit statement of when to use this versus a single-venue quote tool, nor any when-not guidance. The comparison purpose is implied by the framing rather than stated as a selection rule.

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.