Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

coingecko_category_coins

Fetch normalized CoinGecko category coins by slug to list cryptocurrencies in a sector or theme, with optional page, limit, and quote currency filters.

Instructions

CoinGecko category coins. Returns normalized coin rows from a CoinGecko public category page. This endpoint supports the documented vs_currency enum.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoPage number, default 1
slugYesCoinGecko category slug such as stablecoins
limitNoRows to return, default 100, max 100
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

B3.1/5.0
Behavior3/5

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

With no annotations, the description carries the burden, and it does add some value: it labels the source as public and the result as normalized coin rows. It does not disclose pagination behavior, default/max limits, or any caveats, though those are partly visible in the schema.

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 short and easy to scan, but the opening sentence 'CoinGecko category coins' merely restates the tool name and does not carry its weight. The meaningful return statement comes in the second sentence, so it is compact but not optimally front-loaded.

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

Completeness3/5

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

For a simple read-only listing tool, most invocation details are covered: the required slug is documented, and page/limit/vs_currency are described. However, there is no output schema and no description of what fields the normalized rows contain, nor a pointer to coingecko_categories for finding slugs, leaving the description only minimally complete.

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 the schema already explains slug, page, limit, and vs_currency. The description adds no semantic detail beyond noting that the vs_currency enum is supported, which duplicates the schema.

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 second sentence states a concrete action and resource: it returns normalized coin rows from a CoinGecko public category page, which goes beyond the tool name. It does not explicitly contrast with sibling tools like coingecko_categories or coingecko_coin, so it falls short of a 5.

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

Usage Guidelines2/5

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

There is no explicit statement of when to choose this over sibling tools such as coingecko_categories or coingecko_markets. The phrase 'from a CoinGecko public category page' only weakly implies the use case, providing no when-not or alternative routing.

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