Skip to main content
Glama

NS Pros MCP Gateway

nlrb__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": "nlrb__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

A4/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 disclosure burden and does substantial work: it enumerates the 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) and warns that coverage differs by venue with a not_listed answer. It omits auth prerequisites and rate limits, but the operational behavior is well covered.

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 and the density is justified by how many fields the tool returns, but the text is a run-on field enumeration and it is truncated mid-word ('wh'), which leaves the last listed field incomplete. That broken ending costs clarity an agent may need.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema exists, so the description must convey return shape, and it does so field by field across venues along with the equivalence verdict and the not_listed case. The only shortfall is the cut-off final field, which prevents the return contract from being fully specified.

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 the enum values and timestamp format are already documented in the schema. The description restates the asset list and the boundary rule rather than adding meaning beyond it, so it earns the baseline rather than more.

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?

The description opens with a precise verb and resource: it prices 'the same 15-minute crypto up or down window' across polymarket.com, Polymarket US and Kalshi side by side, and flags whether each pair 'is actually the same contract'. That cross-venue equivalence check is a distinctive scope an agent could not infer from the name alone.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It tells the agent exactly what to pass (asset, window with 'current' as default, ISO start on a 15-minute boundary) and states the failure mode for unaligned timestamps plus the not_listed behavior for uncovered assets. It does not name when to prefer this over any other tool, but the sibling set is the same operation under different provider namespaces, so that omission is minor.

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.