Skip to main content
Glama
IAcomunIA

CoinGecko MCP Server

by IAcomunIA

get_tokens_networks_onchain_top_traders

Read-only

Identify top traders for a specific cryptocurrency token by providing its contract address and network to analyze trading activity and performance metrics.

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

Response Schema

{
  $ref: '#/$defs/top_trader_get_response',
  $defs: {
    top_trader_get_response: {
      type: 'object',
      properties: {
        data: {
          type: 'object',
          properties: {
            id: {
              type: 'string'
            },
            attributes: {
              type: 'object',
              properties: {
                traders: {
                  type: 'array',
                  items: {
                    type: 'object',
                    properties: {
                      address: {
                        type: 'string'
                      },
                      average_buy_price_usd: {
                        type: 'string'
                      },
                      average_sell_price_usd: {
                        type: 'string'
                      },
                      explorer_url: {
                        type: 'string'
                      },
                      label: {
                        type: 'string'
                      },
                      name: {
                        type: 'string'
                      },
                      realized_pnl_usd: {
                        type: 'string'
                      },
                      token_balance: {
                        type: 'string'
                      },
                      total_buy_count: {
                        type: 'integer'
                      },
                      total_buy_token_amount: {
                        type: 'string'
                      },
                      total_buy_usd: {
                        type: 'string'
                      },
                      total_sell_count: {
                        type: 'integer'
                      },
                      total_sell_token_amount: {
                        type: 'string'
                      },
                      total_sell_usd: {
                        type: 'string'
                      },
                      type: {
                        type: 'string'
                      },
                      unrealized_pnl_usd: {
                        type: 'string'
                      }
                    }
                  }
                }
              }
            },
            type: {
              type: 'string'
            }
          }
        }
      }
    }
  }
}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
network_idYes
token_addressYes
include_address_labelNoinclude address label data, default: false
sortNosort the traders by field Default value: realized_pnl_usd_desc
tradersNonumber of top token traders 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?

The description adds some behavioral context beyond the annotations: it advises using 'jq_filter' for performance optimization and notes the endpoint queries top traders. However, the annotations already declare 'readOnlyHint: true,' so the agent knows it's a safe read operation. The description doesn't disclose additional traits like rate limits, authentication needs, or data freshness, resulting in a baseline score of 3 for adding minimal value over annotations.

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 a performance tip and purpose statement, but includes an extensive output schema that duplicates structured data. This adds unnecessary length without new value, as the schema could be referenced separately. The core description is concise, but the embedded schema reduces overall efficiency.

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 (6 parameters, read-only operation) and lack of an output schema (though one is embedded in the description), the description is moderately complete. It covers the purpose and a performance tip but lacks details on when to use, behavioral constraints, or parameter nuances. With annotations covering safety, it's adequate but has clear gaps in guidance and context.

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 67%, with four parameters documented (include_address_label, sort, traders, jq_filter) and two not (network_id, token_address). The description mentions 'token contract address on a network,' which hints at the required parameters but doesn't add detailed semantics beyond what the schema provides. Since coverage is moderate (>50%), the baseline is 3, as the description doesn't significantly compensate for gaps.

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 traders based on the provided token contract address on a network.' This specifies the verb ('query'), resource ('top token traders'), and key inputs (token contract address, network). However, it doesn't explicitly differentiate from sibling tools like 'get_tokens_networks_onchain_top_holders' or 'get_tokens_networks_onchain_trades,' which reduces the score from a perfect 5.

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

Usage Guidelines2/5

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

The description provides usage guidance for the 'jq_filter' parameter ('always use... to reduce response size and improve performance'), but offers no guidance on when to use this tool versus alternatives. It doesn't mention sibling tools or clarify the context for selecting this specific query over others, leaving the agent without comparative usage instructions.

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