Skip to main content
Glama

Fetches decentralized exchange liquidity pools for a token

dex_pools
Read-only

Fetches decentralized exchange (DEX) liquidity pools for a token or pair across chains via DexScreener (with GeckoTerminal fallback). Returns chain, DEX name, pair address, base/quote tokens, USD price, liquidity, 24h volume, 24h transaction count, price change percentages, and pool creation age. Limit up to 30 pools. Information only, not financial advice. Price: $0.002 per successful call, paid with x402 (USDC on Base, Solana and 10 more networks); failed calls are not charged.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "token": "<token>"
    },
    "name": "dex_pools"
  }
}

Input Schema

NameRequiredDescriptionDefault
chainNoOptional chain filter (e.g. ethereum, solana, base)
limitNoMaximum number of pools to return (max 30)
tokenYesToken contract address or symbol to search pools for

Output Schema

NameRequiredDescriptionDefault
poolsNo
queryNo
sourceNo
checkedAtNo
disclaimerNo
poolsCountNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations only declare readOnlyHint and openWorldHint, but the description adds meaningful operational context: the primary and fallback providers, the 30-pool cap, the exact fields returned, and a full cost model ($0.002 per successful call, x402 payment, failed calls uncharged). It stops short of describing behavior on empty results, ambiguous symbols, or unwind/refund semantics, which keeps it from a 5.

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?

Purpose and source are front-loaded, followed by the return-field list and then pricing. The sentence is long but each clause carries information, with only minor padding like 'Information only, not financial advice' that occupies space without helping tool selection.

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?

With an output schema present, the return fields need no elaboration, and the description covers provider, cap, and payment model adequately for a read-only lookup tool. The remaining gap is the lack of guidance on indistinguishable token symbols or default chain scope, which matters for a 3-parameter cross-chain search.

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 the schema already documents 'token', 'chain', and 'limit' fully, including the max-30 constraint. The description restates the same facts ('Limit up to 30 pools', 'token or pair') without adding format hints such as ambiguity resolution for symbol input or default chain behavior, so it earns the baseline 3.

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

Purpose4/5

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

States a specific verb and resource ('Fetches decentralized exchange liquidity pools for a token or pair across chains') and names the upstream data sources (DexScreener with GeckoTerminal fallback). It does not explicitly differentiate itself from the sibling 'defi_dex_volume', so an agent must infer that this returns individual pools rather than aggregate volume.

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?

Usage is implied by the phrasing: call it when you need per-pool liquidity/volume data for a token. There is no explicit when-not guidance, no mention of when to prefer 'defi_dex_volume' or the token-specific siblings, and no statement of how a symbol search behaves versus a contract address.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources