Skip to main content
Glama
CoinRithm

CoinRithm/coinrithm-agent-trading

Official
by CoinRithm
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Top 24h crypto movers (universe scan)

get_crypto_movers
Read-only

Scan CoinRithm's tracked crypto universe for top 24h gainers or losers to discover abnormal price moves beyond your watchlist and flag candidates for deeper analysis.

Instructions

Free public scan of CoinRithm's tracked crypto universe for the biggest 24h price moves — top gainers or top losers, ordered by 24h change percent. Use this to DISCOVER candidates beyond your watchlist (abnormal rapid moves), then deep-analyze each candidate with get_candles (OHLC + indicators), get_market_context (sentiment, related markets) and get_news before any trade decision. Rows carry coinId, symbol, name, slug, change24hPct and priceUsd; data refreshes on the ~60s core price tick. Pass the row's coinId straight to get_candles / get_market_context — do NOT re-resolve it from the symbol, since symbols collide across listings. No API key required.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoRows to return, 1-100 (default 20).
directionNoScan direction (default gainers).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
okYes
bodyNo
httpStatusYes
ledgerStatusNo
ledgerEventIdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv0.1.23
    • 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."
  2. Addedv0.1.15

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already cover safety (readOnly, non-destructive, openWorld), and the description adds substantial extra context: free/public, no API key required, ~60s refresh cadence, and the exact row fields returned. This is well beyond the annotation baseline.

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, then usage chain, then field/refresh details. Slightly dense with three trailing sentences, but each carries distinct information (fields, refresh, coinId guidance), so little is wasted.

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 two-optional-param discovery tool with an output schema and read-only annotations, the description covers purpose, usage chain, auth/availability, freshness, and the returned identity fields. Nothing needed to invoke it correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% with both parameters fully described (limit 1-100 default 20, direction enum gainers/losers), so the schema does the heavy lifting. The description mentions gainers/losers and ordering but adds no format or default detail beyond the schema, so baseline 3 applies.

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+resource (scan tracked crypto universe for biggest 24h moves) with scope: top gainers or losers ordered by change percent. It clearly positions itself as a discovery tool distinct from siblings like get_candles and get_market_context, which it names.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly says when to use it ('DISCOVER candidates beyond your watchlist') and which tools to chain afterward (get_candles, get_market_context, get_news) before trading. It even gives a when-not-style warning: do NOT re-resolve coinId from symbol.

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

Deploy Server

Other Tools