Skip to main content
Glama

CoinRithm Agent Trading

by com.coinrithm.mcp
OverviewDiscussionsAdmin

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 size-capped weighted median Yes probability across matched real-money venues, weighted by open interest or else liquidity as weightBasis states, with venueCount and spreadPoints and methodologyVersion — 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. Outcome summaries may include hasObservedPrice and bounded sourceObservation: hasObservedPrice:false means the provider supplied no usable observed price input, while an omitted hasObservedPrice field is unknown; sourceObservation:null means unavailable provenance, not proof that the outcome has no price. Neither field is a live, liquidity, or trading guarantee. priceBasis:'unquoted' (Polymarket/Kalshi) means never traded with no usable book: that probability is not a price. 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

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

NameRequiredDescriptionDefault
okYes
bodyNo
httpStatusYes
ledgerStatusNo
ledgerEventIdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • 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."
  2. Changed1 schema field changed
    • changedInput schema / properties / source / description
      Previous value: -"Venue slug: polymarket, kalshi, rothera, limitless, smarkets, manifold, metaculus, predictit, futuur, myriad, or forecastex."New value: +"Venue slug: polymarket, kalshi, rothera, limitless, smarkets, manifold, metaculus, predictit, futuur, myriad, forecastex, or gemini."
  3. Changed1 schema field changed
    • addedInput schema / properties / detail
      Added value: +{
+  "description": "Response detail: bounded summary (default) or untouched full record.",
+  "enum": [
+    "summary",
+    "full"
+  ],
+  "type": "string"
+}
  4. Changed1 schema field changed
    • changedInput schema / properties / source / description
      Previous value: -"Venue slug: polymarket, kalshi, rothera, limitless, smarkets, manifold, metaculus, predictit, futuur, or myriad."New value: +"Venue slug: polymarket, kalshi, rothera, limitless, smarkets, manifold, metaculus, predictit, futuur, myriad, or forecastex."
  5. Changed1 schema field changed
    • changedInput schema / properties / source / description
      Previous value: -"Venue slug: polymarket, kalshi, metaculus, predictit, limitless, manifold, or smarkets."New value: +"Venue slug: polymarket, kalshi, rothera, limitless, smarkets, manifold, metaculus, predictit, futuur, or myriad."
  6. Added

TDQS

A4.7/5.0
Behavior5/5

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

It discloses behavior well beyond the annotations: the crossSourceMatches and referenceProbability semantics, the default summary bounding with counts preserved, the meaning of hasObservedPrice and sourceObservation nulls, and priceBasis:'unquoted' caveats. This is rich, agent-relevant context not present in the schema or annotations.

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 description is very dense and somewhat unwieldy—long compound sentences packed with caveats. It is front-loaded, but some clauses are hard to parse, and the density reduces scanning efficiency for an agent.

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 output schema exists, the description needn't explain return values, yet it goes further by explaining the semantics of key fields and defaults. It covers what an agent needs to call correctly, including venue/slug, detail mode, and caveats.

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 schema documents all four parameters, but the description adds meaning for detail ('untouched provider-rich record') and for the response fields (crossSourceMatches, referenceProbability) that go beyond the schema. It also names the venue set implied by source.

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 specifies a concrete verb, resource, and scope: 'Free public detail for one prediction-market event by venue + slug,' then enumerates exactly what is returned. It explicitly distinguishes itself from siblings: 'This is the cross-venue research view; for tradability use pm_quote.'

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?

It gives explicit usage guidance: use pm_quote for tradability, and the cross-venue research intent. It also explains when to set detail=full versus the default summary, which is a direct when-to-use instruction.

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