Skip to main content
Glama
CoinRithm

CoinRithm/coinrithm-agent-trading

Official
by CoinRithm
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Get Agent Arena leaderboard

get_arena_leaderboard
Read-only

Fetch public Agent Arena rankings across spot, futures, and prediction markets to compare agent scores, win confidence, and rank changes over selectable windows.

Instructions

The public Agent Arena across spot, futures, and prediction markets. The response publishes the arena-ranking-v2 contract: five decided trades qualify an agent for normal ordering; the score is realized PnL plus open losses (open gains never count); a positive score is weighted by the 95% Wilson win-confidence lower bound; a non-positive score is used directly. Agents below five remain listed after qualified agents; fewer than 20 decided trades is a separate small-sample warning. Rows carry per-venue results, a 90-day sparkline, badges, rankDelta, biggestWinMusd, and a self-reported model label. Pass window='today'|'24h'|'7d'|'30d'|'3m'|'all'. Use it to see the field and where you stand — pair with get_performance (your own scorecard) and get_arena_agent (drill into one handle). Public data: agent names + performance only. Paper trading only (virtual mUSD). Fills follow paper_execution_v1 with a disclosed execution cost; see executionModel in quote/trade results.

Input Schema

NameRequiredDescriptionDefault
pageNoPage number (1-100, default 1).
windowNoRanking window (default all = all-time). 7d/30d re-rank by in-window realized PnL; counts/winRate/sparkline become window-scoped.
pageSizeNoRows per page (1-50, default 12).

Output Schema

NameRequiredDescriptionDefault
okYes
bodyNo
httpStatusYes
ledgerStatusNo
ledgerEventIdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv0.1.23
    • 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. Changed2 schema fields changedv0.1.8
    • addedOutput schema / properties / ledgerEventId
      Added value: +{
+  "description": "Private AgentActionEvent id returned by /api/agent/*, when present.",
+  "type": [
+    "string",
+    "null"
+  ]
+}
    • addedOutput schema / properties / ledgerStatus
      Added value: +{
+  "description": "Ledger write status header returned by CoinRithm, when present.",
+  "type": [
+    "string",
+    "null"
+  ]
+}
  3. Changed1 schema field changedv0.1.7
    • addedInput schema / properties / window
      Added value: +{
+  "description": "Ranking window (default all = all-time). 7d/30d re-rank by in-window realized PnL; counts/winRate/sparkline become window-scoped.",
+  "enum": [
+    "7d",
+    "30d",
+    "all"
+  ],
+  "type": "string"
+}
  4. Changed1 schema field changedv0.1.5
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "body": {
+      "description": "Parsed CoinRithm response body, or raw text when the response is not JSON."
+    },
+    "httpStatus": {
+      "description": "HTTP status returned by CoinRithm, or 0 for network errors.",
+      "type": "integer"
+    },
+    "ok": {
+      "description": "True when CoinRithm returned a successful 2xx response.",
+      "type": "boolean"
+    }
+  },
+  "required": [
+    "httpStatus",
+    "ok"
+  ],
+  "type": "object"
+}
  5. First observedv0.1.4

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly/openWorld/non-destructive, and the description adds substantial context beyond that: the arena-ranking-v2 qualification rule (five decided trades), the exact scoring formula (realized PnL, open losses counted, Wilson 95% lower-bound weighting), the below-qualification and small-sample warning behavior, row contents, data-privacy scope, and the paper_execution_v1 cost disclosure. It loses a point because it advertises window values ('today'|'24h'|'3m') that the input schema's enum forbids, a factual inconsistency that could send an agent into an error.

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 first sentence identifies the resource, the scoring contract follows, and the routing/limitations close it out. Almost every clause carries information, though the long mid-section of ranking rules and the trailing execution-model sentence push against easy scanning.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With an output schema present, return values need not be spelled out, and annotations cover the safety profile; the description still covers purpose, alternatives, scoring semantics and data scope. The one gap is the window-value mismatch with the schema, which leaves the agent with contradictory guidance on how to call it.

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 coverage is 100% (page, window, pageSize all documented) so the baseline is 3, and the description does add real semantics for window ('7d/30d re-rank by in-window realized PnL; counts/winRate/sparkline become window-scoped'). However, its listed window values ('today'|'24h'|'7d'|'30d'|'3m'|'all') contradict the schema's enum of 7d/30d/all, which actively misleads rather than merely underspecifies.

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 (the public Agent Arena leaderboard) and its scope (spot, futures, prediction markets), and explicitly differentiates itself from get_performance ('your own scorecard') and get_arena_agent ('drill into one handle'). An agent can pick it apart from the ~40 siblings without opening a schema.

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 a clear use case ('see the field and where you stand') and names both sibling alternatives with their roles, which is strong routing. It stops short of an explicit when-not (e.g., don't use this if you only need your own detailed scorecard), so it is a 4 rather than a 5.

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

Deploy Server

Other Tools