Skip to main content
Glama

NS Pros MCP Gateway

nvd__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": "nvd__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 it does substantial work: it discloses per-venue output fields including quote_state, spread_pp, volume with its unit, open interest, liquidity, settlement source, and comparison basis, and states that each pair is checked for actual contract equivalence. It also notes that an unaligned timestamp is refused rather than rounded. It omits error, rate-limit, and coverage behavior, and the field enumeration is cut off mid-token, so not a full 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 capabilities and parameters are front-loaded, which is good, but the output field list devolves into an undifferentiated stream and the text terminates abruptly at 'wh', leaving an obviously incomplete sentence. Density is high but the truncation is a real structural defect that an agent cannot recover from.

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?

This is a multi-venue comparison tool with no output schema, so the description must define the return shape, and it attempts to do so via the per-venue field list. However, the list is truncated mid-word, leaving the return spec incomplete, and there is no explanation of what comparison basis means in practice or how conflicting or missing venue quotes are represented. Adequate but with a clear gap given the tool's complexity.

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% and each parameter already documents its allowed values and defaults, so the baseline is 3. The description restates the asset and window options with the same examples and adds only marginal framing. The 'refused, not rounded' behavior for unaligned timestamps appears in both the schema and the description, so it is duplication rather than added meaning.

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 verb-and-resource combination: side-by-side pricing of the same 15-minute crypto up/down window on polymarket.com, Polymarket US and Kalshi, including whether the pairs are actually the same contract. That equivalence check is a distinctive capability an agent can recognize. It stops short of a 5 because no meaningful alternative is named, though the listed siblings are same-named tools in unrelated namespaces.

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 by the parameter requirements: pass an asset and a window to get the comparison. There is no explicit when-to-use versus when-not guidance, no statement of which situations call for a cross-venue comparison rather than a single-venue price, and no prerequisites. An agent can infer applicability but must guess at boundaries.

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.