CoinRithm/coinrithm-agent-trading

Official

by CoinRithm

Overview Schema Source Related Servers Discussions Admin

TypeScript

Hybrid

Close futures position

close_futures_position

DestructiveIdempotent

Close or partially reduce a mock futures position in CoinRithm paper trading; omit fraction for full close or pass a fraction to reduce. Requires trade:futures scope and an idempotency key.

Instructions

Close or partially reduce a mock futures position. fraction in (0,1] reduces partially; omit (or 1) for a full close. idempotencyKey is REQUIRED. Requires the trade:futures scope. 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
`fraction`	No	(0,1] portion to close; omit/1 = full close.
`agentTrace`	No	Optional private trace metadata stored in the caller's ledger.
`positionId`	Yes	Open futures position id to close or reduce.
`idempotencyKey`	Yes	Unique per close 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 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"
+  ]
+}

Changed3 schema fields changedv0.1.5Jun 10, 2026

addedInput schema / properties / idempotencyKey / description

Added value: +"Unique per close intent; reuse replays the original result."

addedInput schema / properties / positionId / description

Added value: +"Open futures position id to close or reduce."

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

Behavior5/5

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

Annotations already declare destructive, idempotent, open-world, non-read-only behavior. The description adds substantial context beyond that: idempotencyKey is REQUIRED, the trade:futures scope is required, it is paper trading only with virtual mUSD, fills follow paper_execution_v1, and there is a disclosed execution cost referenced via executionModel. This goes well beyond what annotations provide.

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?

The description is brief and front-loaded: it states purpose, then fraction semantics, required idempotency, required scope, and execution model in compact sentences. Every sentence contributes actionable information with no repetition.

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?

Given four parameters, a nested agentTrace object, an output schema, and rich annotations, the description covers the essential operational details an agent needs: partial-close semantics, idempotency requirement, required scope, paper-trading context, execution model, and where to find execution cost in results. It is complete without duplicating 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 100%, so parameters are fully documented structurally. The description reinforces the critical non-obvious semantics: fraction in (0,1] reduces partially while omit/1 does a full close, and idempotencyKey is REQUIRED. It adds emphasis on idempotency behavior (reuse replays the original result) beyond the schema text.

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?

The description states a specific verb and resource ('Close or partially reduce a mock futures position') and immediately clarifies the partial-vs-full semantics. It distinguishes the tool from siblings like open_futures_position and cancel_spot_order by stating it closes/reduces futures positions.

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?

It clearly implies when to use the tool (to close or reduce an existing position) and gives the fraction semantics, but does not explicitly name alternatives or state exclusions, e.g., that it cannot close spot orders or PM positions. Conditions are clear enough for selection but lack explicit when-not guidance.

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