Skip to main content
Glama
IAcomunIA

CoinGecko MCP Server

by IAcomunIA

get_coins_top_gainers_losers

Read-only

Identify top 30 cryptocurrencies with largest price gains and losses over specific timeframes to analyze market volatility 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 to query the top 30 coins with largest price gain and loss by a specific time duration

Response Schema

{
  $ref: '#/$defs/top_gainers_loser_get_response',
  $defs: {
    top_gainers_loser_get_response: {
      type: 'object',
      properties: {
        top_gainers: {
          type: 'array',
          items: {
            type: 'object',
            properties: {
              id: {
                type: 'string',
                description: 'coin ID'
              },
              image: {
                type: 'string',
                description: 'coin image url'
              },
              market_cap_rank: {
                type: 'number',
                description: 'coin rank by market cap'
              },
              name: {
                type: 'string',
                description: 'coin name'
              },
              symbol: {
                type: 'string',
                description: 'coin symbol'
              },
              usd: {
                type: 'number',
                description: 'coin price in USD'
              },
              usd_14d_change: {
                type: 'number',
                description: 'coin 14 day change percentage in USD'
              },
              usd_1h_change: {
                type: 'number',
                description: 'coin 1hr change percentage in USD'
              },
              usd_1y_change: {
                type: 'number',
                description: 'coin 1 year change percentage in USD'
              },
              usd_200d_change: {
                type: 'number',
                description: 'coin 200 day change percentage in USD'
              },
              usd_24h_change: {
                type: 'number',
                description: 'coin 24hr change percentage in USD'
              },
              usd_24h_vol: {
                type: 'number',
                description: 'coin 24hr volume in USD'
              },
              usd_30d_change: {
                type: 'number',
                description: 'coin 30 day change percentage in USD'
              },
              usd_7d_change: {
                type: 'number',
                description: 'coin 7 day change percentage in USD'
              }
            }
          }
        },
        top_losers: {
          type: 'array',
          items: {
            type: 'object',
            properties: {
              id: {
                type: 'string',
                description: 'coin ID'
              },
              image: {
                type: 'string',
                description: 'coin image url'
              },
              market_cap_rank: {
                type: 'number',
                description: 'coin rank by market cap'
              },
              name: {
                type: 'string',
                description: 'coin name'
              },
              symbol: {
                type: 'string',
                description: 'coin symbol'
              },
              usd: {
                type: 'number',
                description: 'coin price in USD'
              },
              usd_14d_change: {
                type: 'number',
                description: 'coin 14 day change percentage in USD'
              },
              usd_1h_change: {
                type: 'number',
                description: 'coin 1hr change percentage in USD'
              },
              usd_1y_change: {
                type: 'number',
                description: 'coin 1 year change percentage in USD'
              },
              usd_200d_change: {
                type: 'number',
                description: 'coin 200 day change percentage in USD'
              },
              usd_24h_change: {
                type: 'number',
                description: 'coin 24hr change percentage in USD'
              },
              usd_24h_vol: {
                type: 'number',
                description: 'coin 24hr volume in USD'
              },
              usd_30d_change: {
                type: 'number',
                description: 'coin 30 day change percentage in USD'
              },
              usd_7d_change: {
                type: 'number',
                description: 'coin 7 day change percentage in USD'
              }
            }
          }
        }
      }
    }
  }
}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
vs_currencyYestarget currency of coins *refers to [`/simple/supported_vs_currencies`](/reference/simple-supported-currencies).
durationNofilter result by time range Default value: `24h`
price_change_percentageNoinclude price change percentage timeframe, comma-separated if query more than 1 price change percentage timeframe Valid values: 1h, 24h, 7d, 14d, 30d, 200d, 1y
top_coinsNofilter result by market cap ranking (top 300 to 1000) or all coins (including coins that do not have market cap) Default value: `1000`
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 value by warning about large response sizes and recommending jq_filter for performance, which is useful behavioral context not covered by annotations. However, it doesn't disclose other traits like rate limits, authentication needs, or pagination behavior. No contradiction with annotations exists.

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

Conciseness2/5

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

The description is poorly structured and verbose. It starts with a performance tip about jq_filter, then states the purpose, and includes a full JSON output schema that duplicates information better placed elsewhere. The output schema bloats the description unnecessarily, and the purpose statement is buried. Sentences don't earn their place efficiently, making it harder to scan.

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?

Given the tool's complexity (5 parameters, read-only operation) and lack of output schema in structured fields, the description includes an output schema, which helps. However, it fails to explain key contextual aspects like the meaning of 'top 30' (is it fixed? ranked by what?), how gainers/losers are calculated, or error conditions. The jq_filter advice is useful but doesn't compensate for other gaps.

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 all 5 parameters. The description doesn't add any parameter-specific semantics beyond what's in the schema (e.g., it mentions 'time duration' but doesn't clarify the 'duration' parameter's enum values or interactions). With high schema coverage, the baseline score of 3 is appropriate as the description provides no extra parameter insights.

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 the top 30 coins with largest price gain and loss by a specific time duration.' This specifies the verb ('query'), resource ('top 30 coins'), and scope ('largest price gain and loss by time duration'). However, it doesn't explicitly differentiate from sibling tools like 'get_coins_markets' or 'get_simple_price' that might also provide coin price data.

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 response size and improve performance,' which implies this tool returns large datasets. However, it doesn't specify when to use this tool versus alternatives (e.g., vs. 'get_coins_markets' for broader market data) or mention any prerequisites beyond the required 'vs_currency' parameter. The guidance is practical but incomplete for tool selection.

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