Skip to main content
Glama
coinpaprika

DexPaprika (CoinPaprika)

Official

getNetworkPoolsFilter

Read-onlyIdempotent

Retrieve DEX pools on one network filtered by numeric thresholds like liquidity, volume, transaction count, or creation time, with pagination and sorting.

Instructions

Get pools on one network filtered by numeric thresholds, returned under 'results' with has_next_page and next_cursor. Read-only and keyless. Choose this over getNetworkPools when the user gives numeric constraints or a time window. Use for 'pools over $1M liquidity on Base', 'pools created in the last 24h', or 'high-volume low-liquidity pairs'. Optional filters (AND-combined): volume_24h_min/max, volume_7d_min/max, liquidity_usd_min/max, txns_24h_min, created_after/created_before (Unix timestamps). Also network (required); limit (default 50, max 100); cursor to page; sort_by (default 'volume_usd_24h', alias order_by); sort_dir asc/desc (default 'desc', alias sort).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
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: 50, max: 100)
cursorNoOPTIONAL: Pagination cursor. Pass `next_cursor` from a previous response to fetch the next page. Replaces the old page number.
networkYesREQUIRED: Network ID from getNetworks (e.g., 'ethereum', 'solana')
sort_byNoOPTIONAL (preferred): Field to sort by (default: 'volume_usd_24h'). Prefer the canonical *_24h names; short legacy names are still accepted. 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.
txns_24h_minNoOPTIONAL: Minimum number of transactions in 24h
created_afterNoOPTIONAL: Only pools created after this UNIX timestamp
volume_7d_maxNoOPTIONAL: Maximum 7d volume in USD
volume_7d_minNoOPTIONAL: Minimum 7d volume in USD
created_beforeNoOPTIONAL: Only pools created before this UNIX timestamp
volume_24h_maxNoOPTIONAL: Maximum 24h volume in USD
volume_24h_minNoOPTIONAL: Minimum 24h volume in USD
liquidity_usd_maxNoOPTIONAL: Maximum pool liquidity in USD
liquidity_usd_minNoOPTIONAL: Minimum pool liquidity in USD

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryNo
resultsNo
next_cursorNo
has_next_pageNo
Behavior5/5

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

Discloses read-only, keyless, and pagination structure beyond annotations. Aligns with readOnlyHint and idempotentHint, adding context about rationale logging.

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?

Concise paragraph covering all key aspects, though slightly dense; could be structured with bullet points but remains efficient.

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?

Comprehensive coverage of operation, filters, pagination, sorting, aliases, rationale, and differentiation from sibling. Output schema exists so return values are not needed.

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?

Despite 100% schema coverage, description groups filters, explains defaults, aliases (sort_by/order_by, sort_dir/sort), and provides additional context like AND-combined logic.

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 retrieves pools filtered by numeric thresholds, with pagination details. Differentiates from sibling getNetworkPools by specifying when to choose this tool.

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 advises to use this tool when numeric constraints or time windows are given, and provides example queries. Lists all optional filters and their combination logic.

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