Skip to main content
Glama
Sign In

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. Edge cases: 2 to 5 quotes; each venue is kalshi, polymarket, adi, limitless or myriad with a non-empty identifier; a venue that cannot be read comes back with available false and an error, and spreadPct is null when fewer than 2 quotes resolved. Prices are midpoints, before fees and depth. Not covered: confirming that the identifiers are the same bet (you confirm that), fees, order book depth, and whether the spread can be traded. Use when user asks "is this bet priced differently on Kalshi vs Polymarket?" or "which venue quotes the lowest yes price on this?". Returns: quotes[] (venue, identifier, label, probabilityPct, available, error), availableCount, cheapestVenue, mostExpensiveVenue, spreadPct (percentage points, null if fewer than 2 quotes resolved).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "quotes": "<quotes>"
    },
    "name": "workflow.run_spread_reader"
  }
}

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 read-only/non-destructive/open-world profile, and the description adds real behavioral detail beyond them: no auto-matching of events, per-venue failure yields available=false plus an error, spreadPct is null when fewer than 2 quotes resolve, and prices are midpoints before fees and depth. It could go slightly further on rate limits or latency across venues, which is the one operational trait an agent might still wonder about.

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?

Front-loads the core action and the caller-responsibility caveat early, then layers edge cases and returns. Some redundancy costs it: 'before fees and depth' appears twice, and the 'Returns:' inventory plus the 'Edge cases' block partially restate each other.

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?

With no output schema, the description carries the return shape itself and does so completely — quotes[], availableCount, cheapestVenue, mostExpensiveVenue, spreadPct with its null condition. Combined with the explicit not-covered list (fees, depth, tradability), an agent has everything needed to call it and interpret the result.

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 the baseline is 3, but the description earns extra credit by explaining that quotes[] holds each venue's own identifier type (Kalshi ticker, Polymarket slug) supplied together in one call and that the caller — not the tool — is responsible for confirming they represent the same underlying bet. That is genuinely useful semantics beyond the field descriptions.

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?

Names a specific verb and resource — reading the same bet's live price from 2-5 named venues in one call and reporting the spread between cheapest and most expensive. The venue list (Kalshi, Polymarket, ADI Predictstreet, Limitless, Myriad) and the contrast with workflow.run_odds_converter make it distinguishable from siblings 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 Guidelines5/5

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

Explicitly states when to use it with two verbatim user phrasings ('is this bet priced differently on Kalshi vs Polymarket?', 'which venue quotes the lowest yes price?') and names the alternative for adjacent needs (single-market odds/breakeven/vig → workflow.run_odds_converter). It also draws a clear boundary around what the tool will not do (matching events across venues).

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