CoinRithm Agent Trading

Canonical cross-venue event identity

pm_data_canonical

Read-only

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/inverted/unknown, NEVER price-inferred — plus confidence and provenance basis) and an append-only judgment lineage (created/member_added/member_removed/merged, newest first). 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
`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

A5/5.0

Behavior5/5

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

Discloses free, public, no-API-key behavior; explains merged canonicals still resolve (status='merged', pointer); states NEVER price-inferred. Annotations aligned (readOnly, no destruction).

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Single paragraph front-loaded with core identity. Every sentence adds value—modes, parameters, edge cases, constraints. No redundancy.

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?

Covers all needed behaviors: two operation modes, pagination, merged canonical handling, and safety assurances. Output schema exists, no need to detail returns. Fully adequate.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Adds meaning beyond schema: explains key's dual role (UUID or slug), cursor usage for pagination, limit default (50). Schema coverage is 100% but description enriches with context.

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?

Clearly states it provides a stable cross-venue identity for real-world events, distinguishing from venue-specific slugs. Explicitly describes two modes (list and record-by-key), making purpose unambiguous.

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 to use (track one question across venues) and when not (avoid re-matching slugs). Provides clear usage instructions for both modes and parameter roles.

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?