Skip to main content
Glama
IAcomunIA

CoinGecko MCP Server

by IAcomunIA

get_global

Read-only

Query cryptocurrency global data including active cryptocurrencies, markets, total market cap, and market trends to analyze the overall crypto market.

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 cryptocurrency global data including active cryptocurrencies, markets, total crypto market cap and etc

Response Schema

{
  $ref: '#/$defs/global_get_response',
  $defs: {
    global_get_response: {
      type: 'object',
      properties: {
        data: {
          type: 'object',
          properties: {
            active_cryptocurrencies: {
              type: 'number',
              description: 'number of active cryptocurrencies'
            },
            ended_icos: {
              type: 'number',
              description: 'number of ended icos'
            },
            market_cap_change_percentage_24h_usd: {
              type: 'number',
              description: 'cryptocurrencies market cap change percentage in 24 hours in usd'
            },
            market_cap_percentage: {
              type: 'object',
              description: 'cryptocurrencies market cap percentage',
              properties: {
                btc: {
                  type: 'number'
                },
                eth: {
                  type: 'number'
                }
              }
            },
            markets: {
              type: 'number',
              description: 'number of exchanges'
            },
            ongoing_icos: {
              type: 'number',
              description: 'number of ongoing icos'
            },
            total_market_cap: {
              type: 'object',
              description: 'cryptocurrencies total market cap',
              properties: {
                btc: {
                  type: 'number'
                },
                eth: {
                  type: 'number'
                }
              }
            },
            total_volume: {
              type: 'object',
              description: 'cryptocurrencies total volume',
              properties: {
                btc: {
                  type: 'number'
                },
                eth: {
                  type: 'number'
                }
              }
            },
            upcoming_icos: {
              type: 'number',
              description: 'number of upcoming icos'
            },
            updated_at: {
              type: 'number'
            }
          }
        }
      }
    }
  }
}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
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 behavioral context by emphasizing performance optimization through jq_filter usage and warning about response size, which is valuable. However, it doesn't disclose other traits like rate limits, authentication needs, or error handling, leaving some gaps in behavioral understanding.

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 key usage advice, but it includes an extensive output schema that duplicates structured data, making it verbose. The first two sentences are efficient, but the schema section adds unnecessary bulk, reducing overall conciseness. It could be more streamlined by omitting the schema or summarizing it briefly.

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 low complexity (1 parameter, no required parameters) and annotations covering read-only safety, the description is mostly complete. It explains the purpose, usage guidelines, and includes an output schema (though not needed per rules). However, it lacks details on error cases or integration context, leaving minor gaps for a fully informed agent.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/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 the jq_filter parameter. The description adds semantic value by explaining why to use jq_filter ('to reduce the response size and improve performance') and when to omit it, providing practical guidance beyond the schema's technical details. With only one parameter, this is sufficient for a high score.

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 cryptocurrency global data including active cryptocurrencies, markets, total crypto market cap and etc.' It specifies the verb 'query' and resource 'cryptocurrency global data' with examples. However, it doesn't explicitly differentiate from sibling tools like get_simple_price or get_coins_markets, which also provide cryptocurrency data but with different scopes.

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

Usage Guidelines5/5

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

The description provides explicit usage guidance: '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 tells the agent when to use the parameter and when it might be omitted, offering clear operational advice beyond basic functionality.

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