Skip to main content
Glama

NS Pros MCP Gateway

ntsb-investigations__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": "ntsb-investigations__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/5.0
Behavior2/5

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

No annotations are supplied, so the description must carry the full burden. It does disclose the per-venue return fields (bid/ask/mid/last, spread_pp, quote_state, volume with unit, open interest, liquidity, settlement source, comparison basis), which is useful behavioral context. But it never states that the tool is read-only, whether data is live or cached, how failures or missing venues are reported, and the sentence is cut off mid-word ('wh'), leaving the output contract 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 opening clause and the text is information-dense rather than padded. However, it degenerates into a comma-spliced list and is visibly truncated ('... comparison basis, wh'), so the structure fails at the point where the most important contract-identity information would land.

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

Completeness2/5

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

With no annotations and no output schema, the description is the only place to explain return values and safety characteristics. It hints at the per-venue fields but the enumeration is cut off, and nothing addresses read-only status, freshness, or how non-listed assets and refused timestamps surface to the caller.

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%, so both 'asset' and 'window' are already fully documented, including the unaligned-timestamp refusal. The description restates the asset and window value sets without adding meaning beyond the schema, so the baseline 3 applies.

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 names a specific resource (the same 15-minute crypto up/down window) and a specific action (priced side by side across polymarket.com, Polymarket US and Kalshi), plus the extra judgment it returns (whether each pair is actually the same contract). That is enough for an agent to know what it does, but it never names or distinguishes itself from related tools such as updown_divergence_rate.

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?

It tells the caller which arguments to pass and gives the default window value, and notes the 15-minute boundary constraint, which is implied usage guidance. It gives no explicit when-to-use/when-not-to-use guidance and does not point to any alternative for adjacent questions (e.g., divergence rate).

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.