Skip to main content
Glama

NS Pros MCP Gateway

nplg-catalog__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": "nplg-catalog__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?

With no annotations, the description carries the burden and does substantial work: it names the venues queried, discloses a per-venue quote/microstructure payload (bid/ask/mid/last, spread_pp, quote_state, volume with unit, open interest, liquidity, settlement source, comparison basis) and, importantly, that it reports whether each pair is actually the same contract — a non-obvious behavioral promise. Gaps remain on auth, rate limits, latency, and whether quotes are snapshotted, but the disclosure level is well above baseline.

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?

Front-loading is good: the core comparison is stated first, parameters second, return fields last. However the description is truncated mid-word ('...comparison basis, wh'), leaving a dangling field list, and the long return-field enumeration is dense enough to be a readability cost.

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 returns — and it tries, but the enumeration is cut off, so an agent never learns the full response shape. It also omits how 'next'/'previous' resolve near boundary transitions and whether results are joined per asset-window; these are meaningful omissions 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 coverage is 100%, so the schema already documents asset, window and horizon, including the not_listed and unaligned-timestamp-refused behavior. The description restates the option sets and adds the 15-minute-boundary constraint, which is useful emphasis but not meaningfully beyond the schema — baseline 3 applies.

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?

States a precise verb+resource: pricing the same 15-minute crypto up-or-down window on Polymarket, Polymarket US and Kalshi side by side, plus a same-contract equivalence check. An agent knows exactly what question this tool answers, and the scope (three named venues, 15m windows) distinguishes it from generic comparison siblings.

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 implied through the parameter walkthrough (pass asset and window; current is default), which is enough to call it. But there is no explicit when-to-use/when-not guidance and no routing to related tools such as updown_divergence_rate or archive_compare, so an agent must infer which comparison tool fits.

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.