Skip to main content
Glama

NS Pros MCP Gateway

npi-registry__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": "npi-registry__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 supplied, the description carries the full burden and does substantial work: it enumerates per-venue return fields (question, Up bid/ask/mid/last, spread_pp, quote_state, volume with its unit, open interest, liquidity, settlement source, comparison basis), warns that coverage differs by venue with a not_listed sentinel, and states that an unaligned timestamp is refused rather than rounded. It stops short of explaining auth, rate limits, or what happens when one venue is stale, and the enumeration is cut off mid-word, so the behavioral picture is incomplete at the tail.

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 single dense paragraph of parameters is packed into a run-on sentence, and the description ends abruptly at 'comparison basis, wh', leaving a visibly truncated fragment. The core purpose is front-loaded correctly, but the field enumeration is delivered as a comma-spliced list that is hard to parse and visibly incomplete.

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?

For a comparison tool with no output schema and no annotations, the description does try to enumerate the returned fields and the per-venue caveats, which is the right instinct. However, it is truncated mid-enumeration, so an agent cannot know the full response shape or the final fields, and with no output schema there is no fallback source for that information.

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 all three optional parameters, including defaults, the accepted enum values for asset, and the boundary-alignment rule for window. The description largely restates those values (btc | eth | sol | xrp | bnb, 'current' default, ISO start on a 15-minute boundary), adding only the not_listed coverage caveat, so baseline 3 is warranted.

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?

Opens with a concrete resource and scope: the same 15-minute crypto up/down window priced on polymarket.com, Polymarket US and Kalshi side by side, plus whether each pair is actually the same contract. That is a specific verb+resource an agent can act on, but the description never distinguishes itself from plausible siblings such as updown_divergence_rate or archive_compare, so the agent must infer routing from names alone.

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 rather than stated: the tool is for cross-venue price comparison and contract-equivalence checks, and the schema notes that venues which do not list an asset answer not_listed. There is no explicit when-to-use / when-not-to-use guidance and no named alternative, so an agent knows the shape of the data but not the boundary conditions for choosing this over a sibling.

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.