Skip to main content
Glama
IAcomunIA

CoinGecko MCP Server

by IAcomunIA

get_search_trending

Read-only

Query trending cryptocurrencies, NFTs, and categories on CoinGecko within the last 24 hours to identify popular market movements and investment opportunities.

Instructions

When using this tool, always use the jq_filter parameter to reduce the response size and improve performance.

Only omit if you're sure you don't need the data.

This endpoint allows you query trending search coins, NFTs and categories on CoinGecko in the last 24 hours

Response Schema

{
  $ref: '#/$defs/trending_get_response',
  $defs: {
    trending_get_response: {
      type: 'object',
      properties: {
        categories: {
          type: 'array',
          items: {
            type: 'object',
            properties: {
              id: {
                type: 'number'
              },
              coins_count: {
                type: 'number',
                description: 'category number of coins'
              },
              data: {
                type: 'object',
                properties: {
                  market_cap: {
                    type: 'number',
                    description: 'category market cap'
                  },
                  market_cap_btc: {
                    type: 'number',
                    description: 'category market cap in btc'
                  },
                  market_cap_change_percentage_24h: {
                    type: 'object',
                    description: 'category market cap change percentage in 24 hours',
                    properties: {
                      btc: {
                        type: 'number'
                      },
                      usd: {
                        type: 'number'
                      }
                    }
                  },
                  sparkline: {
                    type: 'string',
                    description: 'category sparkline image url'
                  },
                  total_volume: {
                    type: 'number',
                    description: 'category total volume'
                  },
                  total_volume_btc: {
                    type: 'number',
                    description: 'category total volume in btc'
                  }
                }
              },
              market_cap_1h_change: {
                type: 'number',
                description: 'category market cap 1 hour change'
              },
              name: {
                type: 'string',
                description: 'category name'
              },
              slug: {
                type: 'string',
                description: 'category web slug'
              }
            }
          }
        },
        coins: {
          type: 'array',
          items: {
            type: 'object',
            properties: {
              id: {
                type: 'string',
                description: 'coin ID'
              },
              coin_id: {
                type: 'number'
              },
              data: {
                type: 'object',
                properties: {
                  content: {
                    type: 'string'
                  },
                  market_cap: {
                    type: 'string',
                    description: 'coin market cap in usd'
                  },
                  market_cap_btc: {
                    type: 'string',
                    description: 'coin market cap in btc'
                  },
                  price: {
                    type: 'number',
                    description: 'coin price in usd'
                  },
                  price_btc: {
                    type: 'string',
                    description: 'coin price in btc'
                  },
                  price_change_percentage_24h: {
                    type: 'object',
                    description: 'coin price change percentage in 24 hours',
                    properties: {
                      btc: {
                        type: 'number'
                      },
                      usd: {
                        type: 'number'
                      }
                    }
                  },
                  sparkline: {
                    type: 'string',
                    description: 'coin sparkline image url'
                  },
                  total_volume: {
                    type: 'string',
                    description: 'coin total volume in usd'
                  },
                  total_volume_btc: {
                    type: 'string',
                    description: 'coin total volume in btc'
                  }
                }
              },
              large: {
                type: 'string',
                description: 'coin large image url'
              },
              market_cap_rank: {
                type: 'number',
                description: 'coin market cap rank'
              },
              name: {
                type: 'string',
                description: 'coin name'
              },
              price_btc: {
                type: 'number',
                description: 'coin price in btc'
              },
              score: {
                type: 'number',
                description: 'coin sequence in the list'
              },
              slug: {
                type: 'string',
                description: 'coin web slug'
              },
              small: {
                type: 'string',
                description: 'coin small image url'
              },
              symbol: {
                type: 'string',
                description: 'coin symbol'
              },
              thumb: {
                type: 'string',
                description: 'coin thumb image url'
              }
            }
          }
        },
        nfts: {
          type: 'array',
          items: {
            type: 'object',
            properties: {
              id: {
                type: 'string',
                description: 'NFT collection ID'
              },
              data: {
                type: 'object',
                properties: {
                  content: {
                    type: 'string'
                  },
                  floor_price: {
                    type: 'string',
                    description: 'NFT collection floor price'
                  },
                  floor_price_in_usd_24h_percentage_change: {
                    type: 'string',
                    description: 'NFT collection floor price in usd 24 hours percentage change'
                  },
                  h24_average_sale_price: {
                    type: 'string',
                    description: 'NFT collection 24 hours average sale price'
                  },
                  h24_volume: {
                    type: 'string',
                    description: 'NFT collection volume in 24 hours'
                  },
                  sparkline: {
                    type: 'string',
                    description: 'NFT collection sparkline image url'
                  }
                }
              },
              floor_price_24h_percentage_change: {
                type: 'number',
                description: 'NFT collection floor price 24 hours percentage change'
              },
              floor_price_in_native_currency: {
                type: 'number',
                description: 'NFT collection floor price in native currency'
              },
              name: {
                type: 'string',
                description: 'NFT collection name'
              },
              native_currency_symbol: {
                type: 'string',
                description: 'NFT collection native currency symbol'
              },
              nft_contract_id: {
                type: 'number'
              },
              symbol: {
                type: 'string',
                description: 'NFT collection symbol'
              },
              thumb: {
                type: 'string',
                description: 'NFT collection thumb image url'
              }
            }
          }
        }
      }
    }
  }
}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
show_maxNoshow max number of results available for the given type Available values: `coins`, `nfts`, `categories` Example: `coins` or `coins,nfts,categories`
jq_filterNoA jq filter to apply to the response to include certain fields. Consult the output schema in the tool description to see the fields that are available. For example: to include only the `name` field in every object of a results array, you can provide ".results[].name". For more information, see the [jq documentation](https://jqlang.org/manual/).
Behavior3/5

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

Annotations provide readOnlyHint=true, indicating a safe read operation. The description adds value by mentioning performance considerations (using jq_filter to reduce response size) and specifying the data scope ('last 24 hours'), which aren't covered by annotations. However, it lacks details on rate limits, authentication needs, or pagination behavior, leaving room for improvement in behavioral context.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is relatively concise, with two sentences of guidance followed by the purpose statement. However, it includes an extensive output schema (provided as a response schema in the description text), which is verbose and not strictly necessary since there's no output schema field in the tool definition. This reduces efficiency, but the core description sentences are front-loaded and waste-free.

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?

Given the tool's complexity (querying multiple data types), annotations cover safety (read-only), and the input schema is fully described. The description adds context on performance optimization and temporal scope. However, without an output schema in the tool definition, the embedded response schema in the description compensates but isn't ideal. Overall, it's mostly complete but could better integrate with structured fields.

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 description coverage is 100%, so the input schema fully documents the two parameters (show_max and jq_filter). The description emphasizes using jq_filter for performance but doesn't add semantic details beyond what the schema provides (e.g., examples of jq_filter usage are in the schema). With high schema coverage, the baseline score of 3 is appropriate as the description adds minimal parameter semantics.

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?

The description clearly states the tool's purpose: 'query trending search coins, NFTs and categories on CoinGecko in the last 24 hours.' It specifies the verb ('query'), resource ('trending search coins, NFTs and categories'), and temporal scope ('last 24 hours'). However, it doesn't explicitly differentiate from sibling tools like 'get_search' or 'get_pools_onchain_trending_search,' which prevents a perfect score.

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 provides some usage guidance by recommending to 'always use the `jq_filter` parameter to reduce the response size and improve performance,' with a conditional 'Only omit if you're sure you don't need the data.' This implies a best practice but doesn't specify when to use this tool versus alternatives (e.g., other trending or search tools in the sibling list), nor does it mention prerequisites or exclusions.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/IAcomunIA/MCP_firts'

If you have feedback or need assistance with the MCP directory API, please join our Discord server