CoinRithm/coinrithm-agent-trading

Official

by CoinRithm

Overview Schema Source Related Servers Discussions Admin

TypeScript

Hybrid

Canonical cross-venue event identity

pm_data_canonical

Read-only

Track one prediction-market question across venues by a stable canonical identity instead of re-matching slugs. List active canonicals or fetch one record with members, lineage, and consensus.

Instructions

Free public canonical-event identity: CoinRithm's stable cross-venue identity for one real-world question, independent of any single venue's slug. Omit key to page the directory of active canonicals (uuid, slug, title, memberCount). Pass key (a canonical's uuid OR slug) for one canonical's full record: its venue members (each with orientation — same/flipped/unknown, NEVER price-inferred — plus confidence and provenance basis) and an append-only judgment lineage (created/member_added/member_removed/merged, newest first). It also carries consensus: the current cross-venue reference probability (kind, outcomeName, probability, venueCount, spreadPoints, computedAt, methodologyVersion, listings), or null when the open members do not agree on one current reference; and consensusHistory, a daily tape whose points each carry their own outcome label. listings may be a subset of the contributing venues. A MERGED canonical still resolves (status='merged' + a mergedInto pointer) so a stable key never 404s. Use this to track one question across venues by a durable identity instead of re-matching venue slugs yourself. No API key required.

Input Schema

TableJSON Schema

Name	Required	Description
`key`	No	UUID or slug of one canonical event. Omit to list active canonicals.
`limit`	No	List mode only: max rows (1-200, default 50).
`cursor`	No	List mode only: pagination cursor — pass the previous response's pagination.nextCursor.

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.

Changed5 schema fields changedv0.1.23Oct 2, 2026

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

Addedv0.1.14Aug 13, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Adds substantial behavior beyond the read-only/openWorld annotations: merged canonicals still resolve (status='merged' + mergedInto pointer, never 404s), methodology constraints ('orientation ... NEVER price-inferred'), append-only lineage semantics, and the null-when-disagreement rule for consensus. These are non-obvious operational facts an agent needs.

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?

Dense but front-loaded: the identity statement and list/detail modes come first, with edge-case behavior (merged status, consensus nullability) afterward. Every clause carries information, though the run-on detail about consensus/listings 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?

Even though an output schema exists (so return values needn't be described), the description previews the returned fields and edge-case behavior thoroughly. Combined with the 100% schema coverage and read-only annotations, an agent has everything needed to invoke it correctly.

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 schema already documents `key`, `limit`, and `cursor` including the uuid-or-slug duality. The description reinforces mode binding ('list mode only') but adds no syntax or format detail beyond what the schema already provides, so the baseline 3 applies.

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 resource (cross-venue canonical event identity) and both operating modes: omit `key` to page the active-canonicals directory, pass `key` for one canonical's full record. It clearly differentiates itself from sibling venue-specific tools like pm_data_event/pm_data_events by framing the resource as venue-independent.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives explicit mode selection ('Omit `key` to page...' / 'Pass `key` ... for one canonical's full record') and states the intended use case: 'track one question across venues by a durable identity instead of re-matching venue slugs yourself.' It stops short of naming the specific sibling tools an agent should prefer this over.

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