Skip to main content
Glama
CoinRithm/coinrithm-agent-trading

CoinRithm/coinrithm-agent-trading

Official

Search prediction markets across all venues

pm_data_events
Read-only

Search prediction-market events across 12 venues and compare titles, probabilities, liquidity, status, and source, with outcome previews and cross-venue reference data for research.

Instructions

Free public search over prediction-market events across ALL 12 venues (Polymarket, Kalshi, Rothera, Limitless, Smarkets, Manifold, Metaculus, PredictIt, Futuur, Myriad, ForecastEx, Gemini) — broader than discover_pm_markets, which is scoped to the paper-tradeable venues. Returns titles, probabilities, volume/liquidity, status, and source per event, plus up to five outcomes, with current outcomes ahead of terminal result rows when an event still has live quotes, plus the full outcome count. Use pm_data_event for all outcomes and full evidence. Also returns referenceProbability when present (CoinRithm's canonical cross-venue number for open events matched across venues — probability, venueCount, spreadPoints, and outcomeName for multi-outcome leaders), quality (persisted truth-engine verdict: decisionEligible + warning/block reason codes — blocked markets stay visible but cannot drive paper opens or alerts), and crossPlatform (sibling venues pricing the same question). Research/data only: to trade, use discover_pm_markets + pm_quote instead. No API key required.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "pm_data_events"
  }
}

Input Schema

NameRequiredDescriptionDefault
qNoOptional search text.
fiatNoFiat currency code for monetary figures (default usd).
sortNoOptional sort key.
limitNoMax rows (1-50, default 20).
offsetNoPagination offset (default 0).
sourceNoOptional venue filter: polymarket, kalshi, rothera, limitless, smarkets, manifold, metaculus, predictit, futuur, myriad, forecastex, or gemini.
statusNoStatus filter: open (default), closed, or all. Without it the API's newest-first list starts with long-closed markets.

Output Schema

NameRequiredDescriptionDefault
okYes
bodyNo
httpStatusYes
ledgerStatusNo
ledgerEventIdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.1.26
    • addedInput schema / properties / offset / maximum
      Added value: +9007199254740991
  2. Changed6 schema fields changedv0.1.23
    • changedInput schema / properties / status / description
      Previous value: -"Optional status filter (e.g. open or closed)."New value: +"Status filter: open (default), closed, or all. Without it the API's newest-first list starts with long-closed markets."
    • removedOutput schema / properties / body / description
      Removed value: -"Parsed CoinRithm response body, or raw text when the response is not JSON."
    • removedOutput schema / properties / httpStatus / description
      Removed value: -"HTTP status returned by CoinRithm, or 0 for network errors."
    • removedOutput schema / properties / ledgerEventId / description
      Removed value: -"Private AgentActionEvent id returned by /api/agent/*, when present."
    • removedOutput schema / properties / ledgerStatus / description
      Removed value: -"Ledger write status header returned by CoinRithm, when present."
    • removedOutput schema / properties / ok / description
      Removed value: -"True when CoinRithm returned a successful 2xx response."
  3. Changed1 schema field changedv0.1.14
    • changedInput schema / properties / source / description
      Previous value: -"Optional venue filter: polymarket, kalshi, rothera, limitless, smarkets, manifold, metaculus, predictit, futuur, myriad, or forecastex."New value: +"Optional venue filter: polymarket, kalshi, rothera, limitless, smarkets, manifold, metaculus, predictit, futuur, myriad, forecastex, or gemini."
  4. Changed1 schema field changedv0.1.13
    • changedInput schema / properties / source / description
      Previous value: -"Optional venue filter: polymarket, kalshi, metaculus, predictit, limitless, manifold, or smarkets."New value: +"Optional venue filter: polymarket, kalshi, rothera, limitless, smarkets, manifold, metaculus, predictit, futuur, myriad, or forecastex."
  5. Addedv0.1.12

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already declare readOnly/openWorld/non-destructive, and the description still adds substantive behavior: outcome ordering (live quotes ahead of terminal result rows, capped at five with a total count), quality verdict semantics with decisionEligible and reason codes, blocked markets staying visible, referenceProbability being cross-venue matched, and 'No API key required'. That is real operational context beyond the structured fields.

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?

Purpose, scope, and sibling routing are front-loaded in the first sentence, and the trailing 'Research/data only' clause closes the loop. It is dense and parenthesis-heavy, though, and the long returns sentence overlaps with what the output schema already provides.

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?

An output schema exists, so the description needn't enumerate return fields, yet it does so at length. Everything an agent needs to decide to call this and interpret the response is present; the small leftover gap is the limit-vs-outcomes interaction, which neither schema nor description clarifies.

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 all seven parameters are already documented, including the status default rationale and the source venue list — the description mostly repeats those. It adds little on parameter interaction, notably whether 'limit' bounds events or outcome rows, which is the one ambiguity an agent would want resolved.

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 ('Free public search over prediction-market events') and quantifies scope ('across ALL 12 venues', with the venues enumerated). It explicitly differentiates itself from two siblings: broader than discover_pm_markets (paper-tradeable only) and shallower than pm_data_event (all outcomes).

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 explicit routing rules in both directions: use discover_pm_markets + pm_quote to trade, use pm_data_event for all outcomes and full evidence, and use this one for cross-venue search/research only. It even notes the blocked-market condition ('cannot drive paper opens or alerts'), which is a when-not condition for downstream actions.

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