Skip to main content
Glama
Sign In
DEX Pools MCP

DEX Pools MCP

by kukapay
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

get_trending_pools

Retrieve a formatted table of trending DEX pools across all networks on GeckoTerminal, including key metrics like volume, liquidity, and price.

Instructions

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

Args:
    page: Page number for pagination (default: 1)
    duration: Duration to sort trending list by (options: "5m", "1h", "6h", "24h"; default: "24h")
    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_in_quote, 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_trending_pools"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNo
durationNo24h
includeNobase_token,quote_token,dex,network

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

No annotations are provided, so the description carries the burden. It discloses the return format (formatted table with specific columns) and parameter options with defaults. It implies a read-only operation but does not explicitly state non-mutation, error handling, or rate limits. Still, it offers sufficient behavioral context.

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 well-organized with a clear purpose sentence followed by parameter details. It is slightly verbose with a docstring-like format but remains concise and front-loaded. Every sentence adds value.

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?

The description covers purpose, parameters, and return format adequately. It lacks cross-references to sibling tools or discussion of edge cases, but given the tool's simplicity and the presence of an output schema (described in text), it is mostly complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, but the description fully explains each parameter: page (default 1), duration (options: 5m,1h,6h,24h, default 24h), include (comma-separated attributes with examples). It also describes the output. This adds significant meaning beyond the schema.

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 states 'Query all trending pools across all networks on GeckoTerminal and return a formatted table,' which clearly specifies the verb (query), resource (trending pools), and scope (all networks). This distinguishes it from sibling tools like get_trending_pools_by_network or get_new_pools.

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 trending pools across all networks but does not explicitly state when to use this tool over alternatives or when not to use it. For example, it does not mention get_trending_pools_by_network for network-specific queries. Basic guidance is implied but not explicit.

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

Deploy Server

Other Tools