CoinRithm/coinrithm-agent-trading

Official

by CoinRithm

Overview Schema Source Related Servers Discussions Admin

TypeScript

Hybrid

Search prediction markets across all venues

pm_data_events

Read-only

Search prediction-market events across 12 venues. Returns titles, probabilities, volume, liquidity, status, and up to five outcomes for research and data analysis, not trading.

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.

Input Schema

TableJSON Schema

Name	Required	Description
`q`	No	Optional search text.
`fiat`	No	Fiat currency code for monetary figures (default usd).
`sort`	No	Optional sort key.
`limit`	No	Max rows (1-50, default 20).
`offset`	No	Pagination offset (default 0).
`source`	No	Optional venue filter: polymarket, kalshi, rothera, limitless, smarkets, manifold, metaculus, predictit, futuur, myriad, forecastex, or gemini.
`status`	No	Status filter: open (default), closed, or all. Without it the API's newest-first list starts with long-closed markets.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`ok`	Yes
`body`	No
`httpStatus`	Yes
`ledgerStatus`	No
`ledgerEventId`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedv0.1.23Oct 2, 2026

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."

Changed1 schema field changedv0.1.14Aug 13, 2026

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."

Changed1 schema field changedv0.1.13Jul 15, 2026

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."

Addedv0.1.12Jul 8, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare readOnlyHint/openWorldHint/destructiveHint=false, so safety is covered. The description still adds real behavioral context beyond that: the outcome-ordering rule (live quotes ahead of terminal rows), the referenceProbability and quality verdict semantics (blocked markets stay visible but cannot drive paper opens or alerts), and the no-API-key requirement. It stops short of documenting rate limits or pagination behavior.

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 core scoping distinction is front-loaded well, but the single paragraph then enumerates return fields, referenceProbability internals, and quality reason codes — much of which duplicates the existing output schema. Those sentences do not earn their place given the output schema is present.

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?

For a research/search tool with annotations and an output schema already present, the description covers routing, auth, scope, and notable response behaviors. Nothing an agent needs to select or invoke it correctly is missing.

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 baseline is 3. The description adds venue-scope context but no syntax or format detail for q, fiat, sort, limit, offset, source, or status beyond what the schema already documents, so it neither compensates nor regresses.

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 (search) and resource (prediction-market events) and pins the scope to ALL 12 venues, naming them explicitly. It also differentiates itself from discover_pm_markets (paper-tradeable only) and pm_data_event (all outcomes/full evidence), so an agent can pick the right tool without opening a 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-not: 'Research/data only: to trade, use discover_pm_markets + pm_quote instead,' and routes single-event deep dives to pm_data_event. Both the alternative and the selecting condition are named, leaving nothing to inference.

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