CoinRithm/coinrithm-agent-trading

Official

by CoinRithm

Overview Schema Source Related Servers Discussions Admin

TypeScript

Hybrid

Crypto price for one coin

crypto_price

Read-only

Fetch free public price data for a cryptocurrency by slug, including fiat/USD quote, 24h change, market cap, volume, and optional candles.

Instructions

Free public price for one coin by slug (for example bitcoin): price in fiat and USD, 24h change, high and low, market cap and rank, 24h volume, and freshness. priceUpdatedAt is when the live price was last written; priceStale:true means it is older than priceStaleAfterHours (72), a last known price, not a live one. marketCapSuspect flags a market cap CoinRithm does not trust. price is null for a coin with no live price. fiatApplied:false means the fiat code is not tracked and the values are USD. candles adds bars over that range, merged to at most maxPoints. coinId is the id get_candles and get_market_context take. Unknown slug: 404. No API key required.

Input Schema

TableJSON Schema

Name	Required	Description
`fiat`	No	Currency code such as EUR or JPY (default USD).
`slug`	Yes	Coin slug such as bitcoin or tether-usdt (the slug of a get_crypto_movers row).
`candles`	No	Add bars over this range: 1H (1-minute bars), 1D, 1W, 1M, 3M or 1Y (daily).
`maxPoints`	No	With candles: bars to return, 2-400 (default 24).

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.

Addedv0.1.25Oct 16, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Goes well beyond the readOnly/openWorld/destructive annotations by disclosing stale-price semantics (priceStale, priceStaleAfterHours 72, 'last known not live'), untrusted data (marketCapSuspect), null behavior, fiat fallback (fiatApplied:false), and the 404 unknown-slug outcome.

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?

Front-loaded with the core purpose and packed with terse, high-value clauses. It runs long and blends parameter notes with return-value semantics, but nearly every sentence carries non-redundant information.

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 a multi-flag price tool it covers the edge cases an agent needs (unknown slug 404, null price, stale prices, untrusted market cap, untracked fiat) even though an output schema already exists to describe the shape.

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 the baseline is 3, but the description adds interaction semantics the schema lacks: candles bars are 'merged to at most maxPoints', and the fiat fallback behavior when a code is untracked.

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 verb and resource ('Free public price for one coin by slug') plus the exact payload it returns. An agent can immediately distinguish this spot/crypto price lookup from get_candles, spot_quote, and futures_quote without opening a 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?

Usage is implied rather than stated: 'free public', 'No API key required', and the note that coinId feeds get_candles and get_market_context hint at chaining, but there is no explicit when-to-use-this-vs-alternatives guidance against siblings like spot_quote.

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

Deploy Server