Skip to main content
Glama
kukapay

DEX Pools MCP

by kukapay
OverviewSchemaRelated ServersScoreDiscussions
Python
Remote

get_new_pools_by_network

Retrieve newly created liquidity pools on a specified blockchain network, returning a formatted table with dex, name, price, reserve, volume, and address.

Instructions

Query all the latest pools for a specific network on GeckoTerminal and return a formatted table.

Args:
    network: The network identifier (default: "eth" for Ethereum)
    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, name, base_price_in_quote, reserve_usd, volume_usd_24h, address

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
networkNoeth
pageNo
includeNobase_token,quote_token,dex,network

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Tool Definition Quality

A3.8/5.0
Behavior2/5

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

Describes return format but no annotations provided. No mention of read-only nature, rate limits, or side effects. For a query tool, basic transparency is lacking.

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?

Concise docstring with Args and Returns sections. Every sentence is necessary; no fluff. Efficiently conveys purpose and usage.

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?

Return format is described with columns. However, lacks details on pagination behavior or default page size. Given tool simplicity, it is mostly complete.

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 has 0% description coverage, but description provides defaults and example values for network, page, and include parameters, adding significant value beyond schema types and titles.

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?

Clearly states it queries latest pools for a specific network and returns a formatted table. Differentiates from sibling tools like get_new_pools (no network filter) and get_top_pools_by_network (top vs latest).

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?

Implies usage for network-specific queries via parameter, but no explicit guidance on when to use this vs alternatives like get_new_pools or get_top_pools_by_network. No exclusion criteria.

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/kukapay/dex-pools-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server