CoinRithm/coinrithm-agent-trading

Official

by CoinRithm

Overview Schema Source Related Servers Discussions Admin

TypeScript

Hybrid

Get my trades

get_my_trades

Read-only

Review realized PnL from closed spot, futures, and prediction-market trades. Poll with the updatedSince cursor to surface new stop-loss, take-profit, liquidation, or settlement closes.

Instructions

Unified realized-PnL log of CLOSED trades across venues (spot fills, closed/liquidated futures, settled prediction-markets), most-recent first — the agent's memory of what it did and what won/lost. Use it to review performance before deciding the next move. Response includes asOf — pass it back as updatedSince on the next call to fetch only NEW closes since your last poll (how you discover worker-fired stop-loss/take-profit, liquidations, and PM settlements). Paper trading only (virtual mUSD). Fills follow paper_execution_v1 with a disclosed execution cost; see executionModel in quote/trade results.

Input Schema

TableJSON Schema

Name	Required	Description
`limit`	No	Max rows (1-100, default 25).
`venue`	No	Filter by venue (default all).
`agentTrace`	No	Optional private trace metadata stored in the caller's ledger.
`updatedSince`	No	ISO 8601 cursor: only trades closed/settled since this instant. Pass the previous response's asOf back here.

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

Changed3 schema fields changedv0.1.8Jun 12, 2026

addedInput schema / properties / agentTrace

Added value: +{
+  "additionalProperties": false,
+  "description": "Optional private trace metadata stored in the caller's ledger.",
+  "properties": {
+    "confidence": {
+      "description": "Optional confidence score from 0 to 1.",
+      "maximum": 1,
+      "minimum": 0,
+      "type": "number"
+    },
+    "decisionId": {
+      "description": "Agent decision id for quote/write attribution.",
+      "minLength": 1,
+      "type": "string"
+    },
+    "rationaleSummary": {
+      "description": "Optional concise rationale summary. Do not include chain-of-thought, secrets, or account identity.",
+      "maxLength": 1200,
+      "minLength": 1,
+      "type": "string"
+    },
+    "runId": {
+      "description": "Agent run id for grouping.",
+      "minLength": 1,
+      "type": "string"
+    },
+    "strategyLabel": {
+      "description": "Short strategy label, self-reported by the caller.",
+      "maxLength": 120,
+      "minLength": 1,
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

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"
+  ]
+}

Changed1 schema field changedv0.1.6Jun 10, 2026

addedInput schema / properties / updatedSince

Added value: +{
+  "description": "ISO 8601 cursor: only trades closed/settled since this instant. Pass the previous response's asOf back here.",
+  "type": "string"
+}

Changed1 schema field changedv0.1.5Jun 10, 2026

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"
+}

First observedv0.1.4Jun 10, 2026

TDQS

A4.3/5.0

Behavior5/5

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

Annotations already mark this as a safe read operation, but the description adds substantial behavioral context: paper trading only (virtual mUSD), the paper_execution_v1 execution model with a disclosed cost, the asOf cursor polling pattern, and the kinds of events that appear as new closes.

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 purpose is front-loaded in the first clause, and every sentence carries useful information. It is dense but not padded, though the single long paragraph could be slightly more scannable.

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?

An output schema exists, so return format need not be explained. The description still covers paper-trading scope, the execution model, venue coverage, and the updatedSince polling workflow, making it complete enough for correct invocation.

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 limit, venue, and agentTrace are already documented. The description adds meaning for updatedSince by explaining it should receive the previous response's asOf and why that cursor matters, which goes beyond the schema text.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific resource and scope: CLOSED trades, realized-PnL, across spot/futures/PM venues, most-recent first. It implicitly separates itself from open-order and position tools, but does not explicitly contrast with sibling tools like get_performance or get_agent_ledger.

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 clear usage contexts: review performance before the next move, and poll with updatedSince to discover new closes such as worker-fired stop-loss/take-profit, liquidations, and PM settlements. It lacks explicit when-not-to-use guidance or named alternatives.

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