Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

coingecko_trending

Fetch trending coins and categories from CoinGecko, deduplicated by slug, with optional row limit and quote currency. Returns names, URLs, prices, and 1h/24h/7d changes.

Instructions

CoinGecko trending highlights. Returns trending coins and trending categories from CoinGecko's highlights, deduplicated by slug, each section up to limit rows (default 20, max 50). Items carry name, URL and, where CoinGecko shows them, price in vs_currency and 1h, 24h and 7d percentage changes.

Input Schema

NameRequiredDescriptionDefault
limitNoRows per section to return, default 20, max 50
vs_currencyNoQuote currency

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.17.5
    • addedInput schema / properties / vs_currency / enum
      Added value: +[
+  "btc",
+  "eth",
+  "ltc",
+  "bch",
+  "bnb",
+  "eos",
+  "xrp",
+  "xlm",
+  "link",
+  "dot",
+  "yfi",
+  "sol",
+  "usd",
+  "aed",
+  "ars",
+  "aud",
+  "bdt",
+  "bhd",
+  "bmd",
+  "brl",
+  "cad",
+  "chf",
+  "clp",
+  "cny",
+  "czk",
+  "dkk",
+  "eur",
+  "gbp",
+  "gel",
+  "hkd",
+  "huf",
+  "idr",
+  "ils",
+  "inr",
+  "jpy",
+  "krw",
+  "kwd",
+  "lkr",
+  "mmk",
+  "mxn",
+  "myr",
+  "ngn",
+  "nok",
+  "nzd",
+  "php",
+  "pkr",
+  "pln",
+  "rub",
+  "sar",
+  "sek",
+  "sgd",
+  "thb",
+  "try",
+  "twd",
+  "uah",
+  "vef",
+  "vnd",
+  "zar",
+  "xdr",
+  "xag",
+  "xau",
+  "bits",
+  "sats"
+]
  2. Addedv1.6.0
  3. Removedv1.6.0
  4. First observedv1.0.0

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the full behavioral burden and does disclose meaningful traits: sections are deduplicated by slug, each section is capped at `limit` (default 20, max 50), and items carry name/URL plus optional price and 1h/24h/7d changes. It does not cover pagination, auth, or rate limits, which keeps it out of the top band.

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?

Two sentences, no filler, and the scoping details (deduplication, per-section limit, item fields) are packed efficiently and front-loaded after the one-line purpose statement.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a read-only tool with no annotations and no output schema, the description adequately explains what is returned (two sections, field list, currency-denominated prices). It falls short of full completeness only because it omits any note on return envelope shape or pagination beyond the per-section limit.

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 description coverage is 100%, so both parameters are already documented by the schema (limit default/max, vs_currency as quote currency). The description restates the limit default/max and clarifies that vs_currency controls the price denomination, adding marginal meaning but not exceeding the schema baseline.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb (Returns) and resource (trending coins and trending categories from CoinGecko's highlights), making the tool's function immediately clear. It does not, however, name or contrast itself against the many sibling 'trending'-like tools (coingecko_gainers_losers, coingecko_new_coins, coingecko_categories), so an agent must still infer the distinction.

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 only implied by the word 'trending' and the CoinGecko source. There is no explicit when-to-use vs. alternatives guidance, no mention of when to prefer coingecko_gainers_losers or coingecko_new_coins, and no stated prerequisites or exclusions. Adequate but with a clear routing gap.

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