CoinRithm/coinrithm-agent-trading

Official

by CoinRithm

Overview Schema Source Related Servers Discussions Admin

TypeScript

Hybrid

Get my performance

get_performance

Read-only

Retrieve your agent's realized paper-trading scorecard: total and per-venue PnL, trade counts, and win rate from closed trades.

Instructions

The calling key's own realized performance: total + per-venue realized PnL (mUSD), trade count, win/loss/neutral counts, and win rate (null until there are decided trades). Closed trades only — the scorecard for this agent. 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	Default
`agentTrace`	No	Optional private trace metadata stored in the caller's ledger.

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

Changed4 schema fields changedv0.1.8Jun 12, 2026

addedInput schema / additionalProperties
```
Added value: +false
```

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.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.1/5.0

Behavior5/5

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

Annotations already cover the safety profile (readOnlyHint, destructiveHint=false), and the description layers on real behavioral context: paper trading only with virtual mUSD, fills follow paper_execution_v1 with a disclosed execution cost, and win rate is null until decided trades exist. It even points to executionModel in quote/trade results, which materially affects how an agent should interpret the numbers.

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?

Four sentences, front-loaded with the metric list and then the important scoping caveats (closed trades, paper only, execution cost). Dense with parentheticals and slightly over-stuffed, but every sentence carries information an agent needs.

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 and annotations covering safety, the description only needs to cover semantics the schema cannot: trading mode, closed-trade scoping, and null win-rate behavior, all of which it supplies. The one gap is routing guidance relative to sibling performance/ledger tools.

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?

There is one optional parameter (agentTrace) and schema description coverage is 100%, with the nested runId/decisionId/strategyLabel fields fully documented in the schema. The description adds no parameter-level guidance, so the baseline 3 is appropriate.

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 and scope: the calling key's own realized PnL, per-venue breakdown, trade count, win/loss/neutral counts and win rate, explicitly restricted to closed trades. The realized-only, closed-trades framing cleanly separates it from sibling tools like get_my_trades, get_portfolio, and get_agent_ledger without the agent needing to open any schema.

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

Usage Guidelines3/5

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

The description labels itself 'the scorecard for this agent' and constrains it to closed trades, which implies when it applies, but it never states when to prefer it over get_my_trades, get_equity_curve, or get_agent_ledger, nor any exclusions. Usage is inferred rather than instructed.

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