Skip to main content
Glama
IAcomunIA

CoinGecko MCP Server

by IAcomunIA

get_pools_networks_onchain_info

Read-only

Retrieve detailed metadata for cryptocurrency liquidity pools using contract addresses and network information, including token details, social links, and security 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 pool metadata (base and quote token details, image, socials, websites, description, contract address, etc.) based on a provided pool contract address on a network

Response Schema

{
  $ref: '#/$defs/info_get_response',
  $defs: {
    info_get_response: {
      type: 'object',
      properties: {
        data: {
          type: 'array',
          items: {
            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'
                  }
                }
              }
            }
          }
        },
        included: {
          type: 'array',
          items: {
            type: 'object',
            properties: {
              id: {
                type: 'string'
              },
              attributes: {
                type: 'object',
                properties: {
                  base_token_address: {
                    type: 'string'
                  },
                  community_sus_report: {
                    type: 'number'
                  },
                  quote_token_address: {
                    type: 'string'
                  },
                  sentiment_vote_negative_percentage: {
                    type: 'number'
                  },
                  sentiment_vote_positive_percentage: {
                    type: 'number'
                  }
                }
              },
              type: {
                type: 'string'
              }
            }
          }
        }
      }
    }
  }
}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
networkYes
pool_addressYes
includeNoattributes to include
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 through jq_filter usage and warns about large response sizes. It also implicitly suggests the tool returns detailed metadata, which aligns with the output schema snippet. No contradiction with annotations exists, and the added context is helpful for agent decision-making.

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 statement. However, it includes an extensive output schema (over 100 lines) that duplicates structured data, which is unnecessary and reduces conciseness. The first two sentences are efficient, but the schema bloat makes the overall description verbose and poorly structured for quick comprehension.

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 (4 parameters, 50% schema coverage, no output schema in structured fields), the description is partially complete. It covers parameter semantics and behavioral traits well, but lacks explicit differentiation from sibling tools and doesn't detail the response format beyond the embedded schema. The output schema snippet helps, but it's not integrated into the description effectively, leaving gaps in contextual understanding.

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 'include' and 'jq_filter' having descriptions. The description compensates by explaining the purpose of 'jq_filter' in detail (reducing response size, improving performance) and providing an example usage. It also mentions that pool metadata is queried 'based on a provided pool contract address on a network,' which clarifies the semantics of 'pool_address' and 'network' parameters. This adds meaningful context beyond the schema.

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 pool metadata (base and quote token details, image, socials, websites, description, contract address, etc.) based on a provided pool contract address on a network.' This is a specific verb ('query') with resource ('pool metadata') and scope ('on a network'). However, it doesn't explicitly differentiate from sibling tools like 'get_tokens_networks_onchain_info' or 'get_pools_networks_onchain_trades', which reduces clarity.

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: it strongly recommends using the 'jq_filter' parameter to reduce response size and improve performance, and advises omitting it only if certain data isn't needed. However, it doesn't specify when to use this tool versus alternatives (e.g., 'get_pools_onchain_megafilter' or 'get_search_onchain_pools'), nor does it mention prerequisites like required parameters. The guidance is implied but not comprehensive.

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