Skip to main content
Glama

CoinRithm Agent Trading

by io.github.CoinRithm

Spot quote

spot_quote
Read-only

Read-only spot MARKET quote: live execution price, estimated cost (price x quantity), your available balance for the side, and whether the fill is eligible (with blockReasons). Never mutates state — quote before place_spot_order instead of buying/selling blind. Price age is informational only (a market order fills regardless). coinId is a UCID, NOT a ticker — use resolve_symbol first. 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
NameRequiredDescriptionDefault
sideYesSpot side: buy increases the coin balance; sell reduces it.
coinIdYesCoin UCID (e.g. '1' = BTC).
quantityYesAmount of the base coin (> 0).
agentTraceNoOptional private trace metadata stored in the caller's ledger.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
okYesTrue when CoinRithm returned a successful 2xx response.
bodyNoParsed CoinRithm response body, or raw text when the response is not JSON.
httpStatusYesHTTP status returned by CoinRithm, or 0 for network errors.
ledgerStatusNoLedger write status header returned by CoinRithm, when present.
ledgerEventIdNoPrivate AgentActionEvent id returned by /api/agent/*, when present.

TDQS

A4.4/5.0
Behavior4/5

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

Matches annotations (readOnlyHint=true) and adds details: 'Never mutates state', paper trading specifics, execution cost policy, and that price age is informational. 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.

Conciseness4/5

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

First sentence provides clear core purpose. Subsequent sentences add necessary context but are dense. Could be slightly more concise, but structure is logical and front-loaded.

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?

Covers read-only nature, return value fields, paper trading context, UCID clarification, and ordering guidance. Output schema exists, so return format is not required. Complete for the tool's complexity.

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?

With 100% schema coverage, baseline is 3. Description adds crucial info for coinId ('UCID, not a ticker — use resolve_symbol first') and clarifies side semantics beyond the enum. Other params are adequately described in 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?

Description clearly states 'Read-only spot MARKET quote' and lists specific outputs (execution price, cost, balance, eligibility). Distinguishes from siblings like futures_quote and pm_quote by specifying 'spot' and 'market'.

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?

Explicitly advises to 'quote before place_spot_order instead of buying/selling blind' and to resolve symbols before using coinId. Does not directly compare to siblings but implies when to use by naming the tool it precedes.

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 toolsInspect
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

A4.2/5.0
Disambiguation5/5

Each tool targets a distinct resource or action (e.g., spot vs futures vs PM, quote vs open vs close, different PM data endpoints). Descriptions provide clear context and usage guidance, eliminating ambiguity.

Naming Consistency5/5

All tools follow a verb_noun pattern in snake_case (e.g., `cancel_spot_order`, `open_futures_position`, `pm_data_event`). Even `whoami` is a common exception. Naming is uniform and predictable.

Tool Count4/5

35 tools is on the high side but appropriate for a multi-venue trading platform covering spot, futures, prediction markets, analytics, and account management. Each tool serves a distinct purpose, though minor consolidation could be possible.

Completeness5/5

The tool surface covers the full trading lifecycle: quotes, order placement, cancellation, position management, SL/TP, portfolio tracking, performance, and extensive market data. No obvious gaps for the stated purpose.

Resources