Skip to main content
Glama
coinpaprika

DexPaprika (CoinPaprika)

Official

getDexPools

Read-onlyIdempotent

Retrieve all liquidity pools for a specific DEX on a given network, with sorting and pagination by volume, price, or transactions.

Instructions

Get the pools belonging to one specific DEX on one network, e.g. all Uniswap v3 pools on ethereum, returned under 'pools' with page_info. Read-only and keyless. Narrower than getNetworkPools (a single exchange, not the whole chain). Use for 'show me Raydium pools', 'top pairs on PancakeSwap', or 'liquidity on Orca'. Get the dex id from getNetworkDexes or search first. Params: network (required slug); dex (required id, e.g. 'uniswap_v3'); limit (default 10, max 100); page (default 1); sort_by one of 'volume_usd','price_usd','transactions','last_price_change_usd_24h','created_at' (default 'volume_usd', alias order_by); sort_dir 'asc'/'desc' (default 'desc', alias sort).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dexYesREQUIRED: DEX identifier from getNetworkDexes (e.g., 'uniswap_v3')
pageNoOPTIONAL: Page number for pagination (default: 1, 1-indexed)
sortNoOPTIONAL: alias of sort_dir; both are accepted. Not deprecated at the REST layer: api.dexpaprika.com itself takes sort, so use this name when calling the REST API directly.
limitNoOPTIONAL: Number of items per page (default: 10, max: 100)
networkYesREQUIRED: Network ID from getNetworks (e.g., 'ethereum', 'solana')
sort_byNoOPTIONAL (preferred): Field to sort by (default: 'volume_usd'). The REST API calls this parameter order_by.
order_byNoOPTIONAL: alias of sort_by; both are accepted. Not deprecated at the REST layer: api.dexpaprika.com itself takes order_by, so use this name when calling the REST API directly.
sort_dirNoOPTIONAL (preferred): Sort direction (default: 'desc'). The REST API calls this parameter sort.
rationaleYesREQUIRED. 1-2 sentence rationale for this call (e.g. "User asked for X; calling Y to fetch Z"). Logged for MCP improvement, never shown to end users. No PII or secrets. See the server `instructions` field for the full convention and worked examples.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
poolsNo
page_infoNo
Behavior5/5

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

Adds 'Read-only and keyless' and mentions return structure ('pools' with page_info), complementing annotations (readOnlyHint, idempotentHint).

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?

Well-structured and front-loaded, but slightly lengthy with some redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With output schema present and annotations rich, description covers usage, parameters, and alternatives comprehensively.

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?

Even with 100% schema coverage, description adds context: defaults, sort options, alias explanations, and usage tips.

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?

Description clearly states 'Get the pools belonging to one specific DEX on one network' with examples, distinguishing it from sibling getNetworkPools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly provides use cases ('show me Raydium pools'), prerequisites (get dex id from getNetworkDexes), and notes it's narrower than getNetworkPools.

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/coinpaprika/dexpaprika-mcp'

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