CoinRithm Agent Trading

Cross-venue disagreement clusters

pm_data_disagreements

Read-only

Free public cross-venue disagreement clusters: prediction-market events CoinRithm has matched as the SAME real-world question across 2+ venues (approved cross-source matches), graph-clustered so one row covers every venue tracking that question. Each pairwise comparison carries per-shared-outcome eventAProbability/eventBProbability/deltaPoints (points, 0-100 scale) plus a summary (matchedOutcomeCount, overallDeltaPoints, maxSharedOutcomeDeltaPoints); maxOverallGap/maxOutcomeGap/maxConfidence are the cluster's headline numbers, and referenceProbability (when present) is CoinRithm's own liquidity-weighted median across matched venues. Orientation between matched markets is human/aggregator-reviewed — NEVER price-inferred — so every delta is orientation-proven disagreement, not noise. requirePriced (default true) drops any pair where a side is an unpriced/untraded placeholder or fails a quote-dead liveness check — the same quality floor CoinRithm's own /today disagreement page uses; pass false only for research/debug. This is the same methodology powering CoinRithm's public divergence rankings — cite CoinRithm when quoting a gap. Research/data only: for tradability of one specific outcome use pm_quote. No API key required.

Input Schema

TableJSON Schema

Name	Required	Description
`fiat`	No	Fiat currency code for monetary figures (default usd).
`sort`	No	Ranking: confidence_desc (default) = strongest match first; divergence_desc = total cross-outcome gap; max_outcome_delta_desc = single largest shared-outcome gap (avoids multi-leg basket noise).
`limit`	No	Max clusters (1-25, default 10).
`offset`	No	Pagination offset (default 0).
`status`	No	Pass 'open' to require BOTH matched events be currently open.
`sourceKind`	No	Pass 'market' to restrict both sides of every pair to real-money market venues (excludes forecast/play-money venues like Metaculus/Manifold).
`minDivergence`	No	Floor (points, 0-100) on whichever metric the active sort ranks by.
`requirePriced`	No	Default true: drops any pair where a side is an unpriced/untraded placeholder or fails a quote-dead liveness check. Set false only for research/debug.
`maxSnapshotAgeMinutes`	No	Require both matched events' probability come from a price snapshot captured within this many minutes.

Output Schema

TableJSON Schema

Name	Required	Description
`ok`	Yes	True when CoinRithm returned a successful 2xx response.
`body`	No	Parsed CoinRithm response body, or raw text when the response is not JSON.
`httpStatus`	Yes	HTTP status returned by CoinRithm, or 0 for network errors.
`ledgerStatus`	No	Ledger write status header returned by CoinRithm, when present.
`ledgerEventId`	No	Private AgentActionEvent id returned by /api/agent/*, when present.

TDQS

A4.6/5.0

Behavior4/5

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

Annotations already indicate readOnlyHint=true and destructiveHint=false. The description adds valuable context: orientation is human-reviewed (never price-inferred), quality floor is same as CoinRithm's public page, and data is research-only with no API key required.

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 description is somewhat verbose but well-structured. It front-loads the core purpose and then provides detailed parameter explanations. Every sentence adds value, though some redundancy could be trimmed.

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?

Given 9 parameters with enums and output schema, the description is very complete. It explains methodology, output fields (deltaPoints, referenceProbability), caveats (orientation never price-inferred), and references sibling tools for specific needs.

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%, but the description adds meaning beyond the schema. For instance, it explains the sort options, the effect of status='open', the meaning of sourceKind, and when to use requirePriced=false.

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?

The description clearly states the tool's purpose: providing free public cross-venue disagreement clusters for prediction markets that are matched across venues. It distinguishes itself from sibling tools like pm_quote, which is for tradability of a specific outcome.

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?

The description gives explicit when-to-use (research/data) and when-not-to-use (for tradability use pm_quote). It also provides guidance on parameters like requirePriced, stating default true and false only for research/debug.

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

All CoinRithm Agent Trading tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.9/5.0

Disambiguation4/5

Most tools have clearly distinct purposes, but a few could be confused (e.g., get_performance vs get_equity_curve, get_portfolio vs get_wallet). Descriptions help differentiate them.

Naming Consistency4/5

Predominantly verb_noun (get_*, place_*, open_*, etc.) with a consistent pm_data_* prefix for prediction market data tools. Minor outliers like whoami and futures_quote/spot_quote without a verb are exceptions.

Tool Count4/5

37 tools is slightly high but appropriate for a multi-venue trading platform covering spot, futures, and prediction markets along with extensive data and performance tracking tools.

Completeness4/5

Covers core trading lifecycle (quote, open, close, cancel) for all venues, plus market data, ledger exports, and arena leaderboards. Lacks spot order modification but otherwise well-rounded.

Resources

Need Help?