Skip to main content
Glama
IAcomunIA

CoinGecko MCP Server

by IAcomunIA

get_search_onchain_pools

Read-only

Search for cryptocurrency liquidity pools on specific blockchain networks to find trading pairs, price data, and transaction metrics for analysis.

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 search for pools on a network

Response Schema

{
  $ref: '#/$defs/pool_get_response',
  $defs: {
    pool_get_response: {
      type: 'object',
      properties: {
        data: {
          type: 'array',
          items: {
            type: 'object',
            properties: {
              id: {
                type: 'string'
              },
              attributes: {
                type: 'object',
                properties: {
                  address: {
                    type: 'string'
                  },
                  base_token_price_native_currency: {
                    type: 'string'
                  },
                  base_token_price_quote_token: {
                    type: 'string'
                  },
                  base_token_price_usd: {
                    type: 'string'
                  },
                  fdv_usd: {
                    type: 'string'
                  },
                  market_cap_usd: {
                    type: 'string'
                  },
                  name: {
                    type: 'string'
                  },
                  pool_created_at: {
                    type: 'string'
                  },
                  price_change_percentage: {
                    type: 'object',
                    properties: {
                      h1: {
                        type: 'string'
                      },
                      h24: {
                        type: 'string'
                      },
                      h6: {
                        type: 'string'
                      },
                      m15: {
                        type: 'string'
                      },
                      m30: {
                        type: 'string'
                      },
                      m5: {
                        type: 'string'
                      }
                    }
                  },
                  quote_token_price_base_token: {
                    type: 'string'
                  },
                  quote_token_price_native_currency: {
                    type: 'string'
                  },
                  quote_token_price_usd: {
                    type: 'string'
                  },
                  reserve_in_usd: {
                    type: 'string'
                  },
                  transactions: {
                    type: 'object',
                    properties: {
                      h1: {
                        type: 'object',
                        properties: {
                          buyers: {
                            type: 'integer'
                          },
                          buys: {
                            type: 'integer'
                          },
                          sellers: {
                            type: 'integer'
                          },
                          sells: {
                            type: 'integer'
                          }
                        }
                      },
                      h24: {
                        type: 'object',
                        properties: {
                          buyers: {
                            type: 'integer'
                          },
                          buys: {
                            type: 'integer'
                          },
                          sellers: {
                            type: 'integer'
                          },
                          sells: {
                            type: 'integer'
                          }
                        }
                      },
                      m15: {
                        type: 'object',
                        properties: {
                          buyers: {
                            type: 'integer'
                          },
                          buys: {
                            type: 'integer'
                          },
                          sellers: {
                            type: 'integer'
                          },
                          sells: {
                            type: 'integer'
                          }
                        }
                      },
                      m30: {
                        type: 'object',
                        properties: {
                          buyers: {
                            type: 'integer'
                          },
                          buys: {
                            type: 'integer'
                          },
                          sellers: {
                            type: 'integer'
                          },
                          sells: {
                            type: 'integer'
                          }
                        }
                      },
                      m5: {
                        type: 'object',
                        properties: {
                          buyers: {
                            type: 'integer'
                          },
                          buys: {
                            type: 'integer'
                          },
                          sellers: {
                            type: 'integer'
                          },
                          sells: {
                            type: 'integer'
                          }
                        }
                      }
                    }
                  },
                  volume_usd: {
                    type: 'object',
                    properties: {
                      h1: {
                        type: 'string'
                      },
                      h24: {
                        type: 'string'
                      },
                      h6: {
                        type: 'string'
                      },
                      m15: {
                        type: 'string'
                      },
                      m30: {
                        type: 'string'
                      },
                      m5: {
                        type: 'string'
                      }
                    }
                  }
                }
              },
              relationships: {
                type: 'object',
                properties: {
                  base_token: {
                    type: 'object',
                    properties: {
                      data: {
                        type: 'object',
                        properties: {
                          id: {
                            type: 'string'
                          },
                          type: {
                            type: 'string'
                          }
                        }
                      }
                    }
                  },
                  dex: {
                    type: 'object',
                    properties: {
                      data: {
                        type: 'object',
                        properties: {
                          id: {
                            type: 'string'
                          },
                          type: {
                            type: 'string'
                          }
                        }
                      }
                    }
                  },
                  quote_token: {
                    type: 'object',
                    properties: {
                      data: {
                        type: 'object',
                        properties: {
                          id: {
                            type: 'string'
                          },
                          type: {
                            type: 'string'
                          }
                        }
                      }
                    }
                  }
                }
              },
              type: {
                type: 'string'
              }
            }
          }
        },
        included: {
          type: 'array',
          items: {
            type: 'object',
            properties: {
              id: {
                type: 'string'
              },
              attributes: {
                type: 'object',
                properties: {
                  address: {
                    type: 'string'
                  },
                  coingecko_coin_id: {
                    type: 'string'
                  },
                  decimals: {
                    type: 'integer'
                  },
                  image_url: {
                    type: 'string'
                  },
                  name: {
                    type: 'string'
                  },
                  symbol: {
                    type: 'string'
                  }
                }
              },
              type: {
                type: 'string'
              }
            }
          }
        }
      }
    }
  }
}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
includeNoattributes to include, comma-separated if more than one to include Available values: `base_token`, `quote_token`, `dex`
networkNonetwork ID *refers to [/networks](/reference/networks-list)
pageNopage through results Default value: 1
queryNosearch query
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 a safe read operation. The description adds performance guidance about jq_filter usage and includes a detailed response schema, which helps agents understand output structure. However, it doesn't mention pagination behavior (implied by 'page' parameter), rate limits, or authentication requirements beyond what annotations cover.

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 usage guidance, but includes a lengthy response schema that duplicates what could be in an output schema field. The first three sentences are efficient, but the schema inclusion makes it verbose. Structure could be improved by separating usage notes from technical schema details.

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 5 parameters with full schema coverage, readOnlyHint annotation, and no output schema, the description provides good context. It includes a detailed response schema (compensating for no output schema), usage guidance, and references external documentation. However, it lacks information about pagination limits or error conditions.

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 100%, so parameters are well-documented in the input schema. The description emphasizes jq_filter importance and references the output schema for field availability, adding some value. However, it doesn't explain parameter interactions (e.g., how 'query' and 'include' work together) or provide examples beyond jq_filter.

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

Purpose3/5

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

The description states 'search for pools on a network', which provides a basic verb+resource combination. However, it's vague about search criteria and doesn't distinguish this tool from sibling pool-related tools like 'get_pools_networks_onchain_info' or 'get_pools_onchain_megafilter'. The purpose is understandable but lacks specificity.

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 guidance on when to use the jq_filter parameter ('always use... to reduce response size and improve performance') and when to omit it ('only omit if you're sure you don't need the data'). This gives practical usage advice, though it doesn't specify when to use this tool versus alternative pool search tools among siblings.

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