Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

coingecko_exchanges

List CoinGecko spot, DEX, derivatives, or perp DEX exchanges with rank, name, URL, trust score, and 24h volume, using kind, page, limit, and vs_currency filters.

Instructions

CoinGecko exchanges. Lists CoinGecko exchanges from one table chosen by kind: spot (default), dex, derivatives or perp_dex. Paged with page and limit (default and max 100). Each exchange has rank, id, name, URL, logo, and, where shown, a trust score and 24h volume in vs_currency.

Input Schema

NameRequiredDescriptionDefault
kindNoExchange table kind, default spot
pageNoPage number, default 1
limitNoRows to return, default 100, max 100
vs_currencyNoQuote currency

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.17.5
    • addedInput schema / properties / kind / enum
      Added value: +[
+  "spot",
+  "dex",
+  "derivatives",
+  "perp_dex"
+]
    • 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. First observedv1.0.0

TDQS

A3.7/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It usefully discloses pagination behavior (default and max 100) and the returned fields including the conditional trust score and 24h volume, but says nothing about read-only nature, rate limits, or error behavior for a public data listing.

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?

Three tight sentences, front-loaded with purpose, then the `kind` selector, then pagination and return fields. No filler and every clause carries information.

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?

With no output schema, the description correctly compensates by enumerating the returned fields (rank, id, name, URL, logo, trust score, 24h volume). All four parameters are covered; only operational details like rate limits are absent, which is minor for a read-only list tool.

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?

Schema coverage is 100%, so the baseline is 3, but the description adds real meaning: it links `vs_currency` to the 24h volume figure and ties `kind` to the four selectable tables. This clarifies semantics the schema alone ('Quote currency', 'Exchange table kind') does not.

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?

States a specific verb (Lists) and resource (CoinGecko exchanges) and clarifies that one of four tables is selected via `kind`, which is genuinely discriminating. It does not explicitly distinguish itself from the sibling `coingecko_exchange` (singular detail tool), so it stops 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 Guidelines3/5

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

Usage is implied by 'Lists exchanges from one table chosen by kind' but there is no explicit when-to-use or when-not guidance and no alternative sibling (e.g. coingecko_exchange for a single exchange) is named. Adequate but leaves routing to inference.

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