Skip to main content
Glama

NS Pros MCP Gateway

nsi-bg__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": "nsi-bg__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 present, the description carries the full burden, and it does substantial work: it enumerates the per-venue fields returned (question, bid/ask/mid/last, spread_pp, quote_state, volume with its unit, open interest, liquidity, settlement source, comparison basis) and notes that a venue not listing an asset answers 'not_listed'. It says nothing about authentication, rate limits, caching, or how the contract-equivalence verdict is derived. The final clause is cut off mid-word ('comparison basis, wh'), so the disclosure is incomplete.

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 purpose is front-loaded in the first clause, which is good, but the sentance then runs into a long, comma-spliced list of output fields that terminates mid-word ('wh'). The description is truncated rather than merely long, so the closing enumeration neither completes nor is scoped. Tightening the field list and completing the equivalence sentence would materially help.

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 listing per-venue fields is the right instinct and largely covers the return shape. However, the truncation leaves the comparison-basis explanation unfinished, and nothing explains what 'actually the same contract' means operationally. For a read-only cross-venue comparison with three optional parameters this is adequate but visibly incomplete.

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 the asset enum, the window values including ISO start timestamps, the refusal of unaligned timestamps, and the default. The description restates the same allowed values and the 15-minute boundary rule without adding syntax or format detail beyond what the schema provides. This is the baseline case where the schema does the heavy lifting.

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 specific verb and resource: prices the same 15-minute crypto up/down window on polymarket.com, Polymarket US and Kalshi side by side, and flags whether each pair is actually the same contract. The scope (three named venues, 15-minute crypto windows) is specific enough that an agent can distinguish this from sibling tools such as updown_divergence_rate without opening the schema.

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 only implied through the parameter list: pass asset and window and get a cross-venue comparison. There is no explicit statement of when to choose this over the sibling divergence-rate tool or any other alternative, and no mention of prerequisites or limits on how many windows can be requested. An agent can infer the intended use, but nothing in the text rules out misselection.

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.