Skip to main content
Glama

NS Pros MCP Gateway

nist-standards__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": "nist-standards__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 what each venue entry contains (question, Up bid/ask/mid/last, spread_pp, quote_state, volume with its unit, open interest, liquidity, settlement source, comparison basis) and that it reports whether two quotes are actually the same contract. It does not cover auth needs, rate limits, or how missing venues are represented — though the input schema notes not_listed behavior. The enumeration of return fields is the main value added.

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 opening sentence is well front-loaded and dense with meaning, but the trailing output-field enumeration is a long comma run that ends abruptly mid-word ('wh'), signalling truncation and leaving the reader without a complete list. The parameter sentence sits between the two purposes, slightly interrupting the flow. It is efficient but visibly clipped.

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?

All three parameters are fully specified and the tool is read-only in nature, so basic callability is covered. However, there is no output schema, which makes the description's field list the sole source of return-value information, and that list is cut off at 'wh'. An agent therefore knows the shape of most of the response but not all of it, and gets no guidance on how venues lacking an asset appear in the result.

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%, so both the asset enumeration and the window semantics are already documented in the schema, including the refusal of unaligned timestamps. The description largely restates those enums and the 15-minute boundary rule without adding syntax or edge-case meaning beyond them. Baseline 3 applies when the schema already does 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 description states a concrete resource and scope: the same 15-minute crypto 'up or down' window priced on polymarket.com, Polymarket US and Kalshi, side by side, plus whether the pairs are actually the same contract. That is far more specific than the tool name alone and identifies the venues involved. It stops short of a 5 because there is no verb-first framing and no explicit differentiation from the identically named sibling tools under other providers.

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 context is implied by the 'same window across venues' framing and by the parameter hints (asset, window with 'current' default, 'next', 'previous', or ISO start), but there is no explicit statement of when to prefer this over any alternative, nor any exclusion or prerequisite. The agent can infer the intent but must reason about it rather than read it.

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.