Skip to main content
Glama

Coingecko

by io.github.pipeworx-io

Get Coin

get_coin
Read-onlyIdempotent

Get live cryptocurrency data by CoinGecko ID (e.g., 'bitcoin', 'ethereum'). Returns USD price, market cap, 24h/7d/30d price changes, ATH, circulating supply, and a short description.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesCoinGecko coin ID (lowercase), e.g. "bitcoin", "ethereum", "solana", "dogecoin"

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesCoinGecko coin ID
nameYesFull coin name
symbolYesCoin ticker symbol
ath_usdYesAll-time high price in USD
price_usdYesCurrent price in USD
descriptionYesBrief coin description (up to 500 chars)
total_supplyYesTotal supply amount
change_7d_pctYesPrice change percentage in 7 days
ath_change_pctYesChange from all-time high percentage
change_24h_pctYesPrice change percentage in 24 hours
change_30d_pctYesPrice change percentage in 30 days
market_cap_usdYesMarket capitalization in USD
volume_24h_usdYes24-hour trading volume in USD
market_cap_rankYesRank by market capitalization
circulating_supplyYesCirculating supply amount

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, idempotentHint=true, destructiveHint=false. The description adds value by specifying exact return fields (price, market cap, changes, etc.) and that data is 'live', which complements annotations without contradiction.

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 wasted words. Purpose is front-loaded, then return details are listed. Perfectly concise and well-structured.

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

Completeness5/5

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

Given the simple tool (1 param, safe annotations, and an output schema present), the description is complete. It covers what the agent needs to know without redundancy.

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% on the single 'id' parameter, with a clear description and examples. The tool description reinforces the format (lowercase) and provides examples, adding marginal value beyond the schema.

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

Purpose5/5

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

The description states 'Get live cryptocurrency data by CoinGecko ID' with a specific verb and resource, and lists exact return fields (USD price, market cap, etc.). It clearly distinguishes from sibling tools like search_coins, which are for discovery.

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?

No explicit when-to-use or when-not-to-use guidance is given. The context of sibling tools implies use for specific coin data vs. search_coins for searching, but the description itself does not address usage differentiation.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Coingecko toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.6/5.0
Disambiguation2/5

Several tools are near-duplicates or have heavily overlapping responsibilities (ask_pipeworx / ask_pipeworx_beta / ask_pipeworx_grounded, polymarket_arbitrage / polymarket_edges / polymarket_fill_risk, and ai_visibility_check / scan_competitor_ai_presence). The many meta/entry-point tools (discover_tools, suggest_questions, pipeworx_trending) also blur the boundary between discovery and execution.

Naming Consistency2/5

Tool names mix imperative verb-first patterns (get_coin, search_coins, validate_claim) with noun-phrase labels (bet_research, entity_profile, pipeworx_trending, polymarket_edge_tracker) and inconsistent prefixes. Snake_case is consistent, but the naming grammar and verb styles are not.

Tool Count2/5

35 tools is well past the comfortable range, and the count feels inflated by duplicate routing modes, overlapping polymarket scanners, and generic memory/meta utilities. A server nominally named Coingecko carries only 4 crypto tools while the overwhelming majority belong to unrelated domains.

Completeness2/5

As a CoinGecko server, the surface is severely incomplete: search/get/market/trending exist but historical prices, OHLC, exchanges, categories, and coin details are missing. As a broader data/prediction-market utility it is more expansive, but the lack of a coherent domain makes coverage impossible to assess as a single product.

Resources