Skip to main content
Glama
IAcomunIA

CoinGecko MCP Server

by IAcomunIA

get_tokens_networks_onchain_info

Read-only

Retrieve token metadata including name, symbol, description, social links, and holder information by providing a contract address and network.

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 token metadata (name, symbol, CoinGecko ID, image, socials, websites, description, etc.) based on a provided token contract address on a network

Response Schema

{
  $ref: '#/$defs/info_get_response',
  $defs: {
    info_get_response: {
      type: 'object',
      properties: {
        data: {
          type: 'object',
          properties: {
            id: {
              type: 'string'
            },
            attributes: {
              type: 'object',
              properties: {
                address: {
                  type: 'string'
                },
                categories: {
                  type: 'array',
                  items: {
                    type: 'string'
                  }
                },
                coingecko_coin_id: {
                  type: 'string'
                },
                description: {
                  type: 'string'
                },
                discord_url: {
                  type: 'string'
                },
                farcaster_url: {
                  type: 'string'
                },
                freeze_authority: {
                  type: 'string'
                },
                gt_categories_id: {
                  type: 'array',
                  items: {
                    type: 'string'
                  }
                },
                gt_score: {
                  type: 'number'
                },
                gt_score_details: {
                  type: 'object',
                  properties: {
                    creation: {
                      type: 'number'
                    },
                    holders: {
                      type: 'number'
                    },
                    info: {
                      type: 'number'
                    },
                    pool: {
                      type: 'number'
                    },
                    transaction: {
                      type: 'number'
                    }
                  }
                },
                holders: {
                  type: 'object',
                  properties: {
                    count: {
                      type: 'integer'
                    },
                    distribution_percentage: {
                      type: 'object',
                      properties: {
                        '11_30': {
                          type: 'number'
                        },
                        '31_50': {
                          type: 'number'
                        },
                        rest: {
                          type: 'number'
                        },
                        top_10: {
                          type: 'number'
                        }
                      }
                    },
                    last_updated: {
                      type: 'string'
                    }
                  }
                },
                image: {
                  type: 'object',
                  properties: {
                    large: {
                      type: 'string'
                    },
                    small: {
                      type: 'string'
                    },
                    thumb: {
                      type: 'string'
                    }
                  }
                },
                image_url: {
                  type: 'string'
                },
                is_honeypot: {
                  anyOf: [                    {
                      type: 'boolean'
                    },
                    {
                      type: 'string'
                    }
                  ]
                },
                mint_authority: {
                  type: 'string'
                },
                name: {
                  type: 'string'
                },
                symbol: {
                  type: 'string'
                },
                telegram_handle: {
                  type: 'string'
                },
                twitter_handle: {
                  type: 'string'
                },
                websites: {
                  type: 'array',
                  items: {
                    type: 'string'
                  }
                },
                zora_url: {
                  type: 'string'
                }
              }
            },
            type: {
              type: 'string'
            }
          }
        }
      }
    }
  }
}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
networkYes
addressYes
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 value by emphasizing performance optimization with jq_filter and listing the types of metadata returned (name, symbol, etc.), which goes beyond the annotation. However, it doesn't mention rate limits, authentication needs, or error conditions.

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

Conciseness4/5

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

The description is front-loaded with key usage advice and purpose, followed by a detailed response schema. The first two sentences are highly relevant, but the embedded JSON schema makes it lengthy. However, the schema is necessary given no output schema field, so the structure is appropriate.

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 3 parameters, low schema coverage, no output schema, and annotations only covering read-only status, the description does well by including a full response schema and usage tips. It explains what data is returned and how to filter it, making it fairly complete for a query tool, though it could add more on network/address formats.

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 low at 33%, with only jq_filter having a description. The description compensates by explaining jq_filter's purpose ('reduce response size and improve performance') and listing the metadata fields available, which helps understand what 'address' and 'network' parameters are used for. It doesn't specify format for address or network, but adds meaningful context.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description explicitly states the tool's purpose: 'query token metadata (name, symbol, CoinGecko ID, image, socials, websites, description, etc.) based on a provided token contract address on a network.' This is a specific verb ('query') with clear resources ('token metadata') and distinguishes it from siblings like price or pool tools.

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

Usage Guidelines4/5

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

The description provides clear 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 gives practical advice on parameter usage but doesn't explicitly state when to use this tool versus alternatives like other token info tools in the sibling list.

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