hummingbot-mcp

explore_geckoterminal

Explore DEX market data from GeckoTerminal with no API key required. List networks, DEXes, trending or top pools, pool details, token info, OHLCV candles, and recent trades across multiple blockchains.

Instructions

Explore DEX market data from GeckoTerminal (free, no API key needed).

Progressive discovery flow:
1. action="networks" → List all supported networks (solana, eth, bsc, ...)
2. action="dexes" + network → List DEXes on a network
3. action="trending_pools" (+ network) → Trending pools globally or per network
4. action="top_pools" + network (+ dex_id) → Top pools by volume on a network/dex
5. action="new_pools" (+ network) → Recently created pools
6. action="pool_detail" + network + pool_address → Detailed info for one pool
7. action="multi_pools" + network + pool_addresses → Compare multiple pools
8. action="token_pools" + network + token_address → Top pools for a token
9. action="token_info" + network + token_address → Token details (price, mcap, fdv)
10. action="ohlcv" + network + pool_address → OHLCV candle data
11. action="trades" + network + pool_address → Recent trades

Args:
    action: The data to retrieve.
    network: Network ID (e.g., 'solana', 'eth', 'bsc'). Required for most actions.
    dex_id: DEX ID filter for top_pools (e.g., 'raydium', 'uniswap_v3').
    pool_address: Pool contract address (for pool_detail, ohlcv, trades).
    pool_addresses: List of pool addresses (for multi_pools).
    token_address: Token contract address (for token_pools, token_info).
    timeframe: OHLCV interval (default: '1h'). Options: 1m, 5m, 15m, 1h, 4h, 12h, 1d.
    before_timestamp: Fetch OHLCV candles before this unix timestamp (pagination).
    currency: OHLCV price currency, 'usd' or 'token' (default: 'usd').
    token: Which token's price for OHLCV, 'base' or 'quote' (default: 'base').
    limit: Max OHLCV candles to return (default: 1000).
    trade_volume_filter: Min trade volume in USD to filter trades (optional).

Input Schema

TableJSON Schema

Name	Required	Default
`action`	Yes
`network`	No
`dex_id`	No
`pool_address`	No
`pool_addresses`	No
`token_address`	No
`timeframe`	No	1h
`before_timestamp`	No
`currency`	No	usd
`token`	No	base
`limit`	No
`trade_volume_filter`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.4Apr 29, 2026

TDQS

A3.9/5.0

Behavior3/5

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

With no annotations provided, the description carries the full burden. It states the tool is 'free, no API key needed' and outlines the action flow. However, it does not explicitly confirm read-only behavior, error handling, rate limits, or the impact of invalid parameters. The behavioral disclosure is adequate but not exhaustive.

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-structured: an opening sentence, a numbered action list, then parameter definitions. It is front-loaded with the core purpose. While lengthy due to the number of actions, each sentence is necessary and earns its place. Minor redundancy could be trimmed, but overall it is efficient.

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 the complexity (12 parameters, 11 actions, no output schema), the description covers the tool's functionality comprehensively. It details all actions, required parameters, and optional arguments like timeframe and pagination (before_timestamp). It does not explain the return format, but that is acceptable without an output schema. Overall, it provides sufficient context for an agent to use the tool correctly.

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 schema has 0% description coverage, so the description must compensate. It explains all 12 parameters with examples and default values (e.g., 'network: Network ID (e.g., solana, eth). Required for most actions.'). This adds significant meaning beyond the raw schema, though some parameters like 'token' could benefit from more context about allowed values.

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's purpose: 'Explore DEX market data from GeckoTerminal'. It enumerates 11 distinct actions, each with a brief description, making the capabilities concrete and easy to understand. The name and description together unambiguously identify the tool's scope and resource.

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 a progressive discovery flow and details when to use each action. However, it does not explicitly guide the agent on when to choose this tool over sibling tools like explore_dex_pools. Usage context is implied through the action list but lacks direct comparison or exclusion criteria.

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

Deploy Server

explore_geckoterminal

Instructions

Input Schema

Schema Changelog

TDQS

Other Tools