DEX Pools MCP

Overview Schema Source Related Servers Discussions Admin

get_new_pools

Retrieve the latest DEX liquidity pools across all networks on GeckoTerminal. Filter by attributes and paginate results to get a formatted table.

Instructions

Query all the latest pools across all networks on GeckoTerminal and return a formatted table.

Args:
    page: Page number for pagination (default: 1)
    include: Comma-separated attributes to include (e.g., "base_token,quote_token,dex,network")

Returns:
    Formatted table as a string with columns: dex, network, name, base_price, reserve_usd, volume_usd_24h, address

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_new_pools"
  }
}

Input Schema

Name	Required	Description	Default
`page`	No
`include`	No		base_token,quote_token,dex,network

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0May 26, 2026

TDQS

A4/5.0

Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries the full burden. It discloses that the tool returns a formatted table with specific columns and supports pagination, but does not mention safety traits like being read-only or non-destructive. More context about side effects or limitations would improve transparency.

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

Conciseness5/5

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

The description is two sentences long, with the core purpose in the first sentence. Every sentence adds value: the first describes what the tool does, the second describes parameters. No wasted words.

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?

For a simple query tool with two optional parameters and an output schema (though not detailed), the description covers the return format and parameters. It could mention that it works exclusively on GeckoTerminal (implied by name) and handle error scenarios, but it is sufficiently complete for typical use.

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?

The description explains both parameters: 'Page number for pagination' and 'Comma-separated attributes to include' with an example. This adds meaning beyond the schema type 'integer' and 'string', compensating for the 0% schema description coverage.

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 clearly states the tool queries 'all the latest pools across all networks on GeckoTerminal' and returns a formatted table. It uses a specific verb and resource, distinguishing it from sibling tools like get_new_pools_by_network and get_pool_details.

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 implies usage for getting all pools across networks, but does not explicitly state when not to use it or mention alternatives. For network-specific queries, the sibling get_new_pools_by_network exists, but no guidance is given.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server