CoinRithm Agent Trading

Place spot order

place_spot_order

Place a paper spot order. coinId is a coin UCID, NOT a ticker. orderType market/limit/stop. limitPrice required for limit & stop; stopPrice required for stop. idempotencyKey is REQUIRED and unique per intent (reuse replays the original result — retry a timed-out call with the SAME key; it will never double-execute). Requires the trade:spot scope. CONFIRM with the user before calling. 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
`side`	Yes	Spot side: buy spends USDT; sell spends the base coin.
`coinId`	Yes	Coin UCID (e.g. "1" = BTC).
`quantity`	Yes	Base-coin amount (> 0).
`orderType`	Yes	Order execution type: market, limit, or stop.
`stopPrice`	No	USD trigger — required for stop.
`agentTrace`	No	Optional private trace metadata stored in the caller's ledger.
`limitPrice`	No	USD/coin — required for limit & stop.
`idempotencyKey`	Yes	Unique per intent; reuse replays the original result.

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 changedSep 29, 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 changedJun 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"
+  ]
+}

Changed2 schema fields changedJun 10, 2026

addedInput schema / properties / idempotencyKey

Added value: +{
+  "description": "Unique per intent; reuse replays the original result.",
+  "minLength": 1,
+  "type": "string"
+}

changedInput schema / required

Previous value: -[
-  "coinId",
-  "side",
-  "orderType",
-  "quantity"
-]New value: +[
+  "coinId",
+  "side",
+  "orderType",
+  "quantity",
+  "idempotencyKey"
+]

Changed3 schema fields changedJun 10, 2026

addedInput schema / properties / orderType / description

Added value: +"Order execution type: market, limit, or stop."

addedInput schema / properties / side / description

Added value: +"Spot side: buy spends USDT; sell spends the base coin."

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 observedJun 10, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Goes well beyond the annotations: discloses paper-only settlement in virtual mUSD, the paper_execution_v1 fill model with a disclosed execution cost surfaced via executionModel, and the full retry contract (reuse the SAME idempotencyKey to replay the original result; it never double-executes). This is exactly the mutation/auth/retry context an agent needs for a write tool. Note the tension with idempotentHint=false: the annotation describes distinct-intent calls, while the description explains key-based replay, so this is added nuance rather than a contradiction.

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?

Seven tight sentences, all front-loaded around the action, the disambiguating coin-id warning, conditional parameter rules, the idempotency contract, and the confirmation requirement. No filler and no restatement of the title.

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?

For an 8-parameter write tool with a nested agentTrace object and an output schema, the description covers everything the schema cannot: scope requirement, confirmation policy, paper-vs-live semantics, fill model, and where to read execution cost. Return values are legitimately left to the output schema.

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 already 100%, so the baseline is 3, but the description consolidates the conditional requirements (limitPrice for limit & stop, stopPrice for stop) and adds a high-value warning that coinId is a UCID and NOT a ticker, plus the replay semantics of idempotencyKey that the schema only states tersely.

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?

Specific verb + resource + scope: "Place a paper spot order" immediately separates it from open_futures_position, futures_quote, and spot_quote in the sibling list. The description also pins the mode (paper, virtual mUSD) so an agent cannot mistake it for a live-trading path.

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?

States the precondition (requires trade:spot scope), the human-in-the-loop requirement (CONFIRM with the user before calling), and the execution context (paper only, fills follow paper_execution_v1). It stops short of explicitly naming spot_quote as the preview step, so it is clear context rather than full when/when-not routing.

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

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?