Retrieve normalized cryptocurrency chain rows from CoinGecko's public chains table, filtered by quote currency and row limit for clean JSON output.
CoinGecko chains. Returns normalized chain rows from the CoinGecko public website chains table. This endpoint supports the documented vs_currency enum.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Rows to return, default 100, max 100 | |
| vs_currency | No | Quote currency |
Changes observed during successful MCP inspections.
v1.17.5Input schema / properties / vs_currency / enumAdded 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"
+]v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full behavioral burden. It does disclose that rows are normalized and sourced from a public website table, which weakly implies a read-only public data source, but it does not describe output fields, pagination behavior, or any operational details such as rate limits. The read-only implication is present but not explicit.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is compact and front-loaded with the core behavior. The opening phrase 'CoinGecko chains.' is redundant with the tool name, and 'CoinGecko' appears again in sentence two, but the overall length is appropriate and there is little substantive waste.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
This is a simple optional-parameter list endpoint, so the source and normalization details provide a workable baseline. However, without an output schema, the returned row fields are unspecified, and there is no pagination or usage guidance, leaving an adequate but incomplete definition.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100%: both limit and vs_currency have descriptions in the schema. The description adds nothing beyond the schema for either parameter, only restating that vs_currency is supported, so the baseline 3 applies.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description states a specific action and resource: 'Returns normalized chain rows from the CoinGecko public website chains table.' The plural 'chains' and 'chain rows' helps distinguish it from the sibling coingecko_chain, though it never explicitly names that alternative.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No explicit when-to-use guidance or comparison with alternatives is provided. The description does not mention coingecko_chain for single-chain lookups or explain when this list endpoint is preferred. The only hint is that vs_currency is supported, but the agent is left to infer selection criteria.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.