Skip to main content
Glama
IAcomunIA

CoinGecko MCP Server

by IAcomunIA

get_coins_markets

Read-only

Query cryptocurrency market data including prices, market caps, volumes, and related metrics for analysis and tracking.

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 query all the supported coins with price, market cap, volume and market related data

Response Schema

{
  $ref: '#/$defs/market_get_response',
  $defs: {
    market_get_response: {
      type: 'array',
      items: {
        type: 'object',
        properties: {
          id: {
            type: 'string',
            description: 'coin ID'
          },
          ath: {
            type: 'number',
            description: 'coin all time high (ATH) in currency'
          },
          ath_change_percentage: {
            type: 'number',
            description: 'coin all time high (ATH) change in percentage'
          },
          ath_date: {
            type: 'string',
            description: 'coin all time high (ATH) date',
            format: 'date-time'
          },
          atl: {
            type: 'number',
            description: 'coin all time low (atl) in currency'
          },
          atl_change_percentage: {
            type: 'number',
            description: 'coin all time low (atl) change in percentage'
          },
          atl_date: {
            type: 'string',
            description: 'coin all time low (atl) date',
            format: 'date-time'
          },
          circulating_supply: {
            type: 'number',
            description: 'coin circulating supply'
          },
          current_price: {
            type: 'number',
            description: 'coin current price in currency'
          },
          fully_diluted_valuation: {
            type: 'number',
            description: 'coin fully diluted valuation (fdv) in currency'
          },
          high_24h: {
            type: 'number',
            description: 'coin 24hr price high in currency'
          },
          image: {
            type: 'string',
            description: 'coin image url'
          },
          last_updated: {
            type: 'string',
            description: 'coin last updated timestamp',
            format: 'date-time'
          },
          low_24h: {
            type: 'number',
            description: 'coin 24hr price low in currency'
          },
          market_cap: {
            type: 'number',
            description: 'coin market cap in currency'
          },
          market_cap_change_24h: {
            type: 'number',
            description: 'coin 24hr market cap change in currency'
          },
          market_cap_change_percentage_24h: {
            type: 'number',
            description: 'coin 24hr market cap change in percentage'
          },
          market_cap_rank: {
            type: 'number',
            description: 'coin rank by market cap'
          },
          max_supply: {
            type: 'number',
            description: 'coin max supply'
          },
          name: {
            type: 'string',
            description: 'coin name'
          },
          price_change_24h: {
            type: 'number',
            description: 'coin 24hr price change in currency'
          },
          price_change_percentage_24h: {
            type: 'number',
            description: 'coin 24hr price change in percentage'
          },
          roi: {
            type: 'object',
            description: 'return on investment data',
            properties: {
              currency: {
                type: 'string',
                description: 'ROI currency'
              },
              percentage: {
                type: 'number',
                description: 'ROI percentage'
              },
              times: {
                type: 'number',
                description: 'ROI multiplier'
              }
            },
            required: [              'currency',
              'percentage',
              'times'
            ]
          },
          symbol: {
            type: 'string',
            description: 'coin symbol'
          },
          total_supply: {
            type: 'number',
            description: 'coin total supply'
          },
          total_volume: {
            type: 'number',
            description: 'coin total trading volume in currency'
          }
        }
      }
    }
  }
}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
vs_currencyYestarget currency of coins and market data *refers to [`/simple/supported_vs_currencies`](/reference/simple-supported-currencies).
categoryNofilter based on coins' category *refers to [`/coins/categories/list`](/reference/coins-categories-list).
idsNocoins' IDs, comma-separated if querying more than 1 coin. *refers to [`/coins/list`](/reference/coins-list).
include_tokensNofor `symbols` lookups, specify `all` to include all matching tokens Default `top` returns top-ranked tokens (by market cap or volume)
localeNolanguage background, default: en
namesNocoins' names, comma-separated if querying more than 1 coin.
orderNosort result by field, default: market_cap_desc
pageNopage through results, default: 1
per_pageNototal results per page, default: 100 Valid values: 1...250
precisionNodecimal place for currency price value
price_change_percentageNoinclude price change percentage timeframe, comma-separated if query more than 1 timeframe Valid values: 1h, 24h, 7d, 14d, 30d, 200d, 1y
sparklineNoinclude sparkline 7 days data, default: false
symbolsNocoins' symbols, comma-separated if querying more than 1 coin.
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?

The annotations provide readOnlyHint=true, indicating this is a safe read operation. The description adds performance guidance about using jq_filter to reduce response size, which is useful behavioral context beyond what annotations provide. However, it doesn't mention other behavioral aspects like rate limits, pagination behavior (implied by page/per_page parameters), or authentication requirements.

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 important usage guidance about jq_filter, followed by the core purpose statement. However, it includes a full response schema in the description text that duplicates what should be in an output schema field, making it unnecessarily long and violating the principle that 'every sentence should earn its place.' The performance guidance and purpose statement are concise, but the embedded schema adds bulk.

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 read-only tool with 14 parameters and no output schema, the description provides adequate context about what data is returned and performance considerations. However, it lacks information about response format details, pagination behavior, rate limits, or error conditions that would be helpful given the tool's complexity. The embedded response schema partially compensates for the missing output schema but isn't a proper substitute.

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 already fully documents all 14 parameters. The description doesn't add any parameter-specific information beyond what's in the schema. It mentions jq_filter in a general performance context but doesn't provide additional semantic meaning for any parameters. Baseline 3 is appropriate when schema coverage is complete.

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 states the tool 'allows you to query all the supported coins with price, market cap, volume and market related data', which is a clear verb ('query') and resource ('coins') combination. It specifies the type of data returned (price, market cap, volume, market data), but doesn't explicitly differentiate from sibling tools like 'get_simple_price' or 'get_coins_top_gainers_losers'.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides clear guidance on when to use the jq_filter parameter ('always use...to reduce response size and improve performance') and when to omit it ('Only omit if you're sure you don't need the data'). However, it doesn't provide guidance on when to use this tool versus alternative tools for coin market data among the many sibling tools listed.

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