Skip to main content
Glama

TradingCalc MCP: Options, Forex, Risk Stats, Prediction Markets, On-Chain & Crypto Futures

by io.github.SKalinin909
OverviewDiscussionsAdmin

Spread Reader

workflow.run_spread_reader
Read-only

Reads the same real-world bet's live price from 2-5 prediction-market venues at once (Kalshi, Polymarket, ADI Predictstreet, Limitless, Myriad) in a single call and reports the spread between the cheapest and most expensive. Takes every venue's identifier together in quotes[], for example one Kalshi ticker and one Polymarket slug for the same bet, and returns the venue with the lowest yes midpoint price, before fees and depth. The caller supplies each venue's own identifier for what they've confirmed is the same underlying bet; this tool never auto-matches events across venues, only reads and compares prices for identifiers you provide. For the odds, breakeven win rate or vig of a single market, see workflow.run_odds_converter. Use when user asks "is this bet priced differently on Kalshi vs Polymarket?" or "which venue has the best price on this?". Returns: quotes[] (venue, identifier, label, probabilityPct, available, error), availableCount, cheapestVenue, mostExpensiveVenue, spreadPct (percentage points, null if fewer than 2 quotes resolved).

Input Schema

NameRequiredDescriptionDefault
quotesYesOne entry per venue you want to compare: 2 to 5 total, all in this one call (a Kalshi ticker and a Polymarket slug for the same bet are two entries). Each must genuinely be the same real-world bet; this tool does not verify that for you.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / quotes / description
      Previous value: -"One entry per venue you want to compare: 2 to 5 total. Each must genuinely be the same real-world bet; this tool does not verify that for you."New value: +"One entry per venue you want to compare: 2 to 5 total, all in this one call (a Kalshi ticker and a Polymarket slug for the same bet are two entries). Each must genuinely be the same real-world bet; this tool does not verify that for you."
  2. Changed1 schema field changed
    • addedInput schema / properties / quotes / items / properties / venue / description
      Added value: +"Prediction-market venue this quote comes from"
  3. Changed4 schema fields changed
    • changedInput schema / properties / quotes / description
      Previous value: -"One entry per venue you want to compare: 2 to 4 total. Each must genuinely be the same real-world bet; this tool does not verify that for you."New value: +"One entry per venue you want to compare: 2 to 5 total. Each must genuinely be the same real-world bet; this tool does not verify that for you."
    • changedInput schema / properties / quotes / items / properties / identifier / description
      Previous value: -"Kalshi ticker, Polymarket slug, or ADI Predictstreet symbol, matching the venue field."New value: +"Kalshi ticker, Polymarket slug, ADI Predictstreet symbol, Limitless slug, or Myriad slug, matching the venue field."
    • changedInput schema / properties / quotes / items / properties / venue / enum
      Previous value: -[
-  "kalshi",
-  "polymarket",
-  "adi"
-]New value: +[
+  "kalshi",
+  "polymarket",
+  "adi",
+  "limitless",
+  "myriad"
+]
    • changedInput schema / properties / quotes / maxItems
      Previous value: -4New value: +5
  4. Changed1 schema field changed
    • changedInput schema / properties / quotes / description
      Previous value: -"One entry per venue you want to compare — 2 to 4 total. Each must genuinely be the same real-world bet; this tool does not verify that for you."New value: +"One entry per venue you want to compare: 2 to 4 total. Each must genuinely be the same real-world bet; this tool does not verify that for you."
  5. Added

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, openWorld, non-destructive), and the description adds real operational context: comparison uses yes midpoint before fees and depth, the tool never auto-matches events, and spreadPct is null when fewer than two quotes resolve. It stops short of discussing rate limits or venue availability behavior beyond the per-quote error field.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The core capability and the identifier requirement are front-loaded, and the returns summary is compact. The single dense paragraph is long but nearly every clause carries required information (venue list, spread definition, output fields).

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

Completeness5/5

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

No output schema exists, yet the description enumerates the return shape (quotes[], availableCount, cheapestVenue, mostExpensiveVenue, spreadPct with null semantics). Combined with the readOnly annotations, an agent has everything needed to select and call it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so parameters are already documented; the description nevertheless adds semantic value by explaining that quotes[] takes one venue-native identifier per venue (Kalshi ticker vs Polymarket slug) for the same bet and that the tool does not verify equivalence. That goes beyond the schema's field-level text.

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 ('Reads the same real-world bet's live price from 2-5 prediction-market venues'), enumerates the venues, and names what it computes (the spread). It is clearly distinguishable from siblings like run_odds_converter, which it explicitly points to.

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

Usage Guidelines5/5

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

Gives concrete trigger phrases ('is this bet priced differently on Kalshi vs Polymarket?', 'which venue has the best price?') and explicitly redirects single-market odds/breakeven/vig questions to workflow.run_odds_converter. The no-auto-matching constraint is stated as a usage boundary.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All TradingCalc MCP: Options, Forex, Risk Stats, Prediction Markets, On-Chain & Crypto Futures toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources