Skip to main content
Glama
IAcomunIA

CoinGecko MCP Server

by IAcomunIA

get_search

Read-only

Search for cryptocurrencies, categories, markets, exchanges, and NFTs on CoinGecko to find specific data using queries and filter results for efficiency.

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 to search for coins, categories and markets listed on CoinGecko

Response Schema

{
  $ref: '#/$defs/search_get_response',
  $defs: {
    search_get_response: {
      type: 'object',
      properties: {
        categories: {
          type: 'array',
          items: {
            type: 'object',
            properties: {
              id: {
                type: 'string',
                description: 'category ID'
              },
              name: {
                type: 'string',
                description: 'category name'
              }
            }
          }
        },
        coins: {
          type: 'array',
          items: {
            type: 'object',
            properties: {
              id: {
                type: 'string',
                description: 'coin ID'
              },
              api_symbol: {
                type: 'string',
                description: 'coin api symbol'
              },
              large: {
                type: 'string',
                description: 'coin large image url'
              },
              market_cap_rank: {
                type: 'number',
                description: 'coin market cap rank'
              },
              name: {
                type: 'string',
                description: 'coin name'
              },
              symbol: {
                type: 'string',
                description: 'coin symbol'
              },
              thumb: {
                type: 'string',
                description: 'coin thumb image url'
              }
            }
          }
        },
        exchanges: {
          type: 'array',
          items: {
            type: 'object',
            properties: {
              id: {
                type: 'string',
                description: 'exchange ID'
              },
              large: {
                type: 'string',
                description: 'exchange large image url'
              },
              market_type: {
                type: 'string',
                description: 'exchange market type'
              },
              name: {
                type: 'string',
                description: 'exchange name'
              },
              thumb: {
                type: 'string',
                description: 'exchange thumb image url'
              }
            }
          }
        },
        icos: {
          type: 'array',
          items: {
            type: 'string'
          }
        },
        nfts: {
          type: 'array',
          items: {
            type: 'object',
            properties: {
              id: {
                type: 'string',
                description: 'NFT collection ID'
              },
              name: {
                type: 'string',
                description: 'NFT name'
              },
              symbol: {
                type: 'string',
                description: 'NFT collection symbol'
              },
              thumb: {
                type: 'string',
                description: 'NFT collection thumb image url'
              }
            }
          }
        }
      }
    }
  }
}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYessearch query
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/).
Behavior4/5

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

Annotations declare readOnlyHint=true, which the description aligns with by describing a search operation. The description adds valuable behavioral context beyond annotations: performance advice (use jq_filter to reduce response size), a caution (omit only if sure not needed), and details on response structure (coins, categories, markets, etc.). No contradiction with annotations.

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

Conciseness3/5

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

The description is front-loaded with usage advice but includes an extensive embedded JSON output schema that duplicates structured data, reducing conciseness. The first two sentences are efficient, but the schema adds bulk without earning its place in the description text.

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 moderate complexity (search with performance tuning), 100% schema coverage, and readOnlyHint annotation, the description is fairly complete. It explains the search scope, provides behavioral tips, and details response structure via embedded schema. However, no output schema is provided separately, so the embedded one compensates adequately.

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 schema fully documents both parameters ('query' and 'jq_filter'). The description adds minimal param semantics beyond the schema—it emphasizes jq_filter's importance but doesn't explain syntax or format details. Baseline 3 is appropriate as the schema handles most documentation.

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 searches for 'coins, categories and markets listed on CoinGecko' with a specific verb ('search') and resource scope. It distinguishes from some siblings (e.g., 'get_search_onchain_pools', 'get_search_trending') by specifying the search domain, though not all alternatives are explicitly named.

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 implied usage guidance by emphasizing the 'jq_filter' parameter for performance and listing searchable entities (coins, categories, markets). However, it lacks explicit when-to-use vs. alternatives (e.g., 'search_docs' or other 'get_search_*' tools) or clear exclusions, leaving some ambiguity.

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