Fetch a cryptocurrency profile, market stats, links, and categories by coin id; choose a quote currency to view market values in preferred units.
CoinGecko coin profile. Returns CoinGecko profile, market stats, links, and categories for one coin id. This endpoint supports the documented vs_currency enum and is not intended for real-time trading.
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | CoinGecko coin id such as bitcoin | |
| 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?
No annotations are provided, so the description carries the full behavioral burden. It discloses the returned sections and adds a meaningful caveat that data is 'not intended for real-time trading,' hinting at staleness. It omits auth needs, rate limits, and error behavior for an invalid id.
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?
Three tight sentences, front-loaded with the resource name and followed by return contents and a caveat. No filler or repetition; slightly compacted further would be even better.
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?
With no output schema and no annotations, the description adequately covers what is returned and the non-real-time caveat. It stops short of routing to sibling CoinGecko endpoints, leaving an ambiguity for an agent choosing between single-coin, markets, and analysis tools.
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 description coverage is 100%, so both params are already documented in the schema; baseline 3 applies. The description reinforces that `id` addresses a single coin and that `vs_currency` uses a documented enum, but adds no format or default details beyond the schema.
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?
States a specific verb and resource: returns CoinGecko profile, market stats, links, and categories for one coin id. An agent knows exactly what content comes back and the single-lookup scope. However, it does not mention the close sibling coingecko_coin_analysis, so sibling differentiation is left to inference.
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?
There is a light implicit cue ('for one coin id') and a negative caveat ('not intended for real-time trading'), but no explicit when-to-use, when-not-to-use, or named alternatives such as coingecko_coin_analysis or coingecko_search. The agent is left to guess which CoinGecko endpoint fits a given request.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.