Skip to main content
Glama
IAcomunIA

CoinGecko MCP Server

by IAcomunIA

get_tokens_networks_onchain_holders_chart

Read-only

Retrieve historical token holder data for a specific contract address on a blockchain network to analyze distribution trends over time.

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 get the historical token holders chart based on the provided token contract address on a network

Response Schema

{
  $ref: '#/$defs/holders_chart_get_response',
  $defs: {
    holders_chart_get_response: {
      type: 'object',
      properties: {
        data: {
          type: 'object',
          properties: {
            id: {
              type: 'string'
            },
            attributes: {
              type: 'object',
              properties: {
                token_holders_list: {
                  type: 'array',
                  items: {
                    type: 'array',
                    items: {
                      type: 'string'
                    }
                  }
                }
              }
            },
            type: {
              type: 'string'
            }
          }
        },
        meta: {
          type: 'object',
          properties: {
            token: {
              type: 'object',
              properties: {
                address: {
                  type: 'string'
                },
                coingecko_coin_id: {
                  type: 'string'
                },
                name: {
                  type: 'string'
                },
                symbol: {
                  type: 'string'
                }
              }
            }
          }
        }
      }
    }
  }
}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
networkYes
token_addressYes
daysNonumber of days to return the historical token holders chart Default value: 7
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 provide readOnlyHint=true, indicating a safe read operation. The description adds valuable behavioral context beyond annotations: it emphasizes performance optimization with 'jq_filter', warns about response size, and specifies the tool returns historical data (not real-time). It doesn't cover rate limits, authentication needs, or pagination, but given annotations cover safety, this adds meaningful context.

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 performance advice, followed by the core purpose. However, it includes an embedded JSON output schema that duplicates information better placed in structured fields, adding bulk without earning its place in the description text. The first two sentences are efficient, but the schema inclusion reduces overall conciseness.

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 has annotations (readOnlyHint), moderate parameter complexity (4 params, 2 required), and no output schema, the description provides sufficient context: it clarifies the tool's purpose, offers usage tips, and references the response structure. It could improve by explaining the 'days' enum options or differentiating from siblings, but it covers key aspects for a read-only historical data tool.

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 50%, with only 'days' and 'jq_filter' having descriptions. The description compensates by explaining the purpose of 'jq_filter' in reducing response size and improving performance, and it references the output schema for available fields. It doesn't detail 'network' or 'token_address' parameters, but the tool's purpose implies their roles, and the schema covers required fields adequately.

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 'get the historical token holders chart based on the provided token contract address on a network', which clearly specifies the verb ('get'), resource ('historical token holders chart'), and key inputs (token address, network). It distinguishes from most siblings by focusing on holders data rather than prices, pools, or other metrics, though it doesn't explicitly differentiate from similar tools like 'get_tokens_networks_onchain_top_holders'.

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 includes a performance tip about using 'jq_filter' to reduce response size, which provides some usage guidance. However, it doesn't specify when to use this tool versus alternatives (e.g., 'get_tokens_networks_onchain_top_holders' for current top holders vs. historical chart), nor does it mention prerequisites or exclusions. The guidance is implied rather than explicit.

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