Skip to main content
Glama

CoinRithm Agent Trading

by io.github.CoinRithm

Get prediction-market event detail

pm_data_event
Read-only

Free public detail for one prediction-market event by venue + slug: outcomes with probabilities, price snapshots, resolution evidence, crossSourceMatches (the SAME real-world question priced on other venues — read probability divergence directly from it), referenceProbability when present (CoinRithm's canonical cross-venue number: the liquidity-weighted median Yes probability across matched real-money venues, with venueCount and spreadPoints — quote all three together, venues disagree and the spread says by how much), recent whale trades on the event, related events, related news, and volumeHistory when present (daily volume points captured since 2026-07-02 — read the event's volume trend directly from it). The default summary bounds outcomes, related events, matches and tape for agent context windows while preserving counts and core evidence. Set detail=full only when the untouched provider-rich record is needed. This is the cross-venue research view; for tradability use pm_quote. No API key required.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
fiatNoFiat currency code for monetary figures (default usd).
slugYesEvent slug on that venue.
detailNoResponse detail: bounded summary (default) or untouched full record.
sourceYesVenue slug: polymarket, kalshi, rothera, limitless, smarkets, manifold, metaculus, predictit, futuur, myriad, forecastex, or gemini.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
okYesTrue when CoinRithm returned a successful 2xx response.
bodyNoParsed CoinRithm response body, or raw text when the response is not JSON.
httpStatusYesHTTP status returned by CoinRithm, or 0 for network errors.
ledgerStatusNoLedger write status header returned by CoinRithm, when present.
ledgerEventIdNoPrivate 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 declare readOnlyHint and openWorldHint; the description adds that no API key is required and explains how to interpret key output fields (crossSourceMatches, referenceProbability). This adds value beyond annotations, though it does not mention potential rate limits.

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 long but well-structured, front-loading the main purpose and key fields, then providing usage advice. Every sentence adds value, though it could be slightly more concise without losing information.

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 the complexity, schema coverage, existence of output schema, and sibling tools, the description thoroughly covers what the tool returns, how to use it, and how it relates to other tools (pm_quote, pm_data_*), making it complete for an AI agent.

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 context for the detail parameter (default vs full) and implies the source and slug are identifiers. It goes beyond schema by explaining when to use different parameter values, earning above baseline.

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 provides free public details for one prediction-market event by venue and slug, listing specific return fields (outcomes, probabilities, etc.) and distinguishing it from pm_quote for tradability.

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 tells when to use this tool ('cross-venue research view') and when to use alternatives ('for tradability use pm_quote'), along with guidance on using the detail parameter ('Set detail=full only when the untouched provider-rich record is needed').

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 toolsInspect
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

A4.2/5.0
Disambiguation5/5

Each tool targets a distinct resource or action (e.g., spot vs futures vs PM, quote vs open vs close, different PM data endpoints). Descriptions provide clear context and usage guidance, eliminating ambiguity.

Naming Consistency5/5

All tools follow a verb_noun pattern in snake_case (e.g., `cancel_spot_order`, `open_futures_position`, `pm_data_event`). Even `whoami` is a common exception. Naming is uniform and predictable.

Tool Count4/5

35 tools is on the high side but appropriate for a multi-venue trading platform covering spot, futures, prediction markets, analytics, and account management. Each tool serves a distinct purpose, though minor consolidation could be possible.

Completeness5/5

The tool surface covers the full trading lifecycle: quotes, order placement, cancellation, position management, SL/TP, portfolio tracking, performance, and extensive market data. No obvious gaps for the stated purpose.

Resources