Skip to main content
Glama

CryptoData API

by io.github.elevasyncsolutions-jpg

get_trending

Trending coins on CoinGecko (api_key required).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
api_keyNoYour API key from register()

Schema Changelog

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

  1. Changed1 schema field changed
    • changedInput schema / properties / api_key / description
      Previous value: -"Optional — for billing"New value: +"Your API key from register()"
  2. Changed2 schema fields changed
    • addedInput schema / properties / api_key / description
      Added value: +"Optional — for billing"
    • changedInput schema / required
      Previous value: -[
-  "api_key"
-]New value: +[]
  3. Changed1 schema field changed
    • removedInput schema / properties / api_key / description
      Removed value: -"Your API key"
  4. First observed

TDQS

A3.5/5.0
Behavior2/5

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

No annotations are provided, so the description bears full responsibility. It only discloses the API key requirement, but lacks details on rate limits, error handling, response size, or whether it is read-only. This minimal disclosure is insufficient.

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?

A single sentence that is direct and without any fluff. Every word is necessary and the structure is optimal for quick understanding.

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 tool with one parameter and no output schema, the description provides the core purpose and a prerequisite. However, it lacks details on what the response contains (e.g., top trending coins, time frame) and does not differentiate among multiple trending-related sibling tools, leaving the agent with incomplete context.

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 coverage is 100%, and the description merely repeats the requirement for an API key without adding new semantics. The schema already documents the parameter with a similar description, so the description adds no extra value beyond the baseline.

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 clearly states the tool retrieves trending coins on CoinGecko, specifying the resource and distinguishing it from siblings like get_meme_trending and trending_categories.

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?

The description mentions that an API key is required, which serves as a usage prerequisite. However, it does not provide explicit guidance on when to use this tool versus alternatives like get_meme_trending, nor does it specify when not to use it.

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

All CryptoData API 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

C2.8/5.0
Disambiguation4/5

Tools generally have distinct purposes, but some overlap exists between price history tools (get_ohlc vs get_price_summary) and meme-related tools (analyze vs scan vs trending). Overall, descriptions help differentiate.

Naming Consistency5/5

All tool names follow a consistent snake_case verb_noun pattern (e.g., get_price, set_price_alert, analyze_contract). No mixing of conventions.

Tool Count3/5

48 tools is on the higher side, but it covers a broad spectrum of crypto data (prices, DeFi, sentiment, alerts, etc.) and each tool seems justified. However, the count could be slimmed down by grouping similar functions.

Completeness4/5

Very comprehensive coverage of crypto data: prices, market stats, DeFi, sentiment, gas, alerts, portfolio, arbitrage, token analysis. Minor gaps like NFT data or direct exchange rate queries.

Resources