Skip to main content
Glama

NS Pros MCP Gateway

nist-fluid-properties__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-fluid-properties__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

B3.3/5.0
Behavior3/5

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

No annotations exist, so the description carries the whole burden. It does disclose genuine behavior: that a venue not listing the asset answers not_listed, that unaligned timestamps are refused rather than rounded, and that the response reports quote_state, spread in percentage points, volume with its unit, and a comparison basis for contract equivalence. However, the response enumeration is cut off mid-word ('comparison basis, wh'), leaving the return shape incomplete and no statement of latency, rate limits, or failure modes when a venue is unreachable.

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 subject and the three-venue scope are correctly front-loaded in the first sentence, and the second sentence efficiently covers parameter usage. But the trailing 'Per venue:' list is a dense, comma-spliced enumeration that terminates in a truncated fragment ('wh'), which is a real structural defect rather than mere brevity.

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 output schema and no annotations, the description must explain both behavior and returns, and it attempts to do so field by field. The truncation leaves the response contract incomplete, and there is no mention of what happens if a venue errors or how freshness/last-update is conveyed, so an agent cannot fully predict the payload.

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 all three parameters are already documented with defaults, enums, and the ISO-8601 boundary rule. The description largely restates the same asset list and window values rather than adding new meaning such as the interpretation of horizon or the effect of combined asset/window choices. Baseline 3 is appropriate when the schema 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 opening clause states a specific verb-like action and resource: price the same 15-minute crypto up-or-down window across polymarket.com, Polymarket US and Kalshi side by side, plus whether each pair is actually the same contract. That is far more specific than the sibling names alone, which look like duplicated copies of the same tool. It does not name or exclude any specific alternative tool, so it stops short of a 5.

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 guidance ('current' is the default, 'next'/'previous'/ISO start accepted, unaligned timestamps refused), which tells an agent how to frame a request. There is no explicit statement of when to reach for this tool versus a sibling such as a divergence-rate or archive-compare tool, and no prerequisites or exclusions are given.

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.