Skip to main content
Glama
IAcomunIA

CoinGecko MCP Server

by IAcomunIA

get_tokens_networks_onchain_top_holders

Read-only

Query top token holders by contract address and network to analyze token distribution and ownership patterns.

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

Response Schema

{
  $ref: '#/$defs/top_holder_get_response',
  $defs: {
    top_holder_get_response: {
      type: 'object',
      properties: {
        data: {
          type: 'object',
          properties: {
            id: {
              type: 'string'
            },
            attributes: {
              type: 'object',
              properties: {
                holders: {
                  type: 'array',
                  items: {
                    type: 'object',
                    properties: {
                      address: {
                        type: 'string'
                      },
                      amount: {
                        type: 'string'
                      },
                      label: {
                        type: 'string'
                      },
                      percentage: {
                        type: 'string'
                      },
                      rank: {
                        type: 'number'
                      },
                      value: {
                        type: 'string'
                      }
                    }
                  }
                },
                last_updated_at: {
                  type: 'string'
                }
              }
            },
            type: {
              type: 'string'
            }
          }
        }
      }
    }
  }
}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
networkYes
addressYes
holdersNonumber of top token holders to return, you may use any integer or `max` Default value: 10
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 this is a safe read operation. The description adds useful behavioral context: it emphasizes performance optimization through jq_filter and mentions the response includes holders with specific fields (address, amount, etc.) via the embedded schema. However, it doesn't disclose rate limits, authentication needs, or data freshness details (beyond last_updated_at in schema). The description doesn't contradict annotations.

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: it starts with a performance tip about jq_filter before stating the core purpose, and includes a full JSON output schema inline, which is redundant and verbose. The output schema should be in a separate field, not in the description. Sentences are useful but not front-loaded, and the embedded schema adds unnecessary length.

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 complexity (4 parameters, read-only operation) and lack of output schema in structured fields, the description includes an output schema, which helps. However, it's embedded in the description rather than provided separately, and key contextual details like rate limits, error handling, or pagination are missing. The annotations cover safety, but more behavioral context is needed for full completeness.

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 50% (2 of 4 parameters have descriptions). The description doesn't add meaningful parameter semantics beyond what's in the schema: it mentions jq_filter but repeats schema guidance, and doesn't explain network/address parameters. With moderate schema coverage, the baseline is 3, as the description doesn't compensate for the undocumented parameters (network, address).

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 top token holders based on the provided token contract address on a network'. This is a specific verb+resource combination that distinguishes it from most siblings (e.g., get_tokens_networks_onchain_info, get_tokens_networks_onchain_pools). However, it doesn't explicitly differentiate from get_tokens_networks_onchain_holders_chart, which appears related but not identical.

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 emphasizing the jq_filter parameter for performance and stating 'Only omit if you're sure you don't need the data.' This implies a recommended practice but doesn't specify when to use this tool versus alternatives like get_tokens_networks_onchain_holders_chart or other holder-related tools. No explicit when-not-to-use or prerequisite information is provided.

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