CoinRithm Agent Trading

Get OHLCV candles

get_candles

Read-only

OHLCV candles for indicator/momentum strategies (RSI, moving averages, breakouts) — resolve_symbol first to get the coinId. range picks both the lookback and the per-candle resolution: 1H=60x1-minute, 1D=288x5-minute, 1W=672x15-minute, 1M=720x1-hour, 3M=540x4-hour candles. Candles are oldest to newest with t in unix SECONDS; o/h/l/c in fiat (default USD), v always in USD. Paper trading only — virtual funds (50,000 mUSD). Not financial advice. Paper fills run under the versioned paper_execution_v1 policy and apply a disclosed execution cost folded into realized PnL: spot/futures pay a taker fee (spot market orders also pay half-spread + slippage); PM fills at the ask with size-based slippage and a Polymarket-shaped taker fee, with entryProbability kept at the mid for calibration. See the executionModel in quote/trade results — a rehearsal cost, not an exchange fill guarantee.

Input Schema

TableJSON Schema

Name	Required	Description
`fiat`	No	Quote currency for o/h/l/c (default USD).
`range`	No	Lookback + resolution (default 1D = 288 five-minute candles).
`coinId`	Yes	Coin UCID (e.g. "1" = BTC). Use resolve_symbol to find it.
`agentTrace`	No	Optional private trace metadata stored in the caller's ledger.

Output Schema

TableJSON Schema

Name	Required	Description
`ok`	Yes	True when CoinRithm returned a successful 2xx response.
`body`	No	Parsed CoinRithm response body, or raw text when the response is not JSON.
`httpStatus`	Yes	HTTP status returned by CoinRithm, or 0 for network errors.
`ledgerStatus`	No	Ledger write status header returned by CoinRithm, when present.
`ledgerEventId`	No	Private AgentActionEvent id returned by /api/agent/*, when present.

TDQS

A4.5/5.0

Behavior5/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, destructiveHint=false. The description adds significant detail: paper trading, virtual funds, execution model (paper_execution_v1 policy), costs, and candle ordering. No contradictions.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is quite long, with detailed execution model information that may be extraneous for a candle retrieval tool. However, it is well-structured with front-loaded purpose and clear sections.

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 the complexity (4 params, output schema exists), the description covers usage, behavioral traits, parameter meanings, and trade execution context. It is complete for an agent to invoke correctly.

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%. Description adds meaning for 'range' by specifying exact lookback and resolution mappings (e.g., 1H=60x1-minute). For 'coinId', it says to use resolve_symbol. For 'fiat', it notes default USD. Adds value beyond schema.

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 clearly states it provides OHLCV candles for indicator/momentum strategies like RSI, moving averages, breakouts. It also instructs to resolve_symbol first to get coinId, distinguishing it from tools that don't require pre-resolution.

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?

The description explains when to use (for indicator/momentum strategies) and provides prerequisites (resolve_symbol). It mentions paper trading only and virtual funds, but does not explicitly exclude when not to use compared to siblings.

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

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.9/5.0

Disambiguation4/5

Most tools have clearly distinct purposes, but a few could be confused (e.g., get_performance vs get_equity_curve, get_portfolio vs get_wallet). Descriptions help differentiate them.

Naming Consistency4/5

Predominantly verb_noun (get_*, place_*, open_*, etc.) with a consistent pm_data_* prefix for prediction market data tools. Minor outliers like whoami and futures_quote/spot_quote without a verb are exceptions.

Tool Count4/5

37 tools is slightly high but appropriate for a multi-venue trading platform covering spot, futures, and prediction markets along with extensive data and performance tracking tools.

Completeness4/5

Covers core trading lifecycle (quote, open, close, cancel) for all venues, plus market data, ledger exports, and arena leaderboards. Lacks spot order modification but otherwise well-rounded.

Resources

Need Help?