Skip to main content
Glama
DexPaprika (CoinPaprika)

DexPaprika (CoinPaprika)

Official

getNetworkPoolsFilter

Read-onlyIdempotent

Filter DEX pools on a network by liquidity, 24h/7d volume, transaction count, or creation time to find pools such as those over $1M liquidity on Base or created in the last 24h.

Instructions

Get pools on one network filtered by numeric thresholds, returned under 'results' with has_next_page and next_cursor. Read-only. The first page works without an API key; paging with cursor needs a key (a free key pages without limit). 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'. Without a Dev plan or higher (a Dev, Pro or Enterprise key on api-pro.dexpaprika.com), pools created in the last hour are left out, so a created_after window shorter than an hour comes back empty. Optional filters (AND-combined): volume_24h_min/max, volume_7d_min/max, liquidity_usd_min/max, txns_24h_min, created_after/created_before (a relative offset such as '-24h', Unix seconds, RFC3339 or YYYY-MM-DD). 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).

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": {
      "network": "<network>",
      "rationale": "<rationale>"
    },
    "name": "getNetworkPoolsFilter"
  }
}

Input 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; needs an API key (a free key pages without limit). 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 at or after this time: a relative offset such as '-24h' or '-7d', Unix seconds, RFC3339 or YYYY-MM-DD. Without a Dev plan or higher, pools created in the last hour are left out, so a window shorter than an hour comes back empty.
volume_7d_maxNoOPTIONAL: Maximum 7d volume in USD
volume_7d_minNoOPTIONAL: Minimum 7d volume in USD
created_beforeNoOPTIONAL: Only pools created at or before this time, same formats as created_after (e.g. '-1h')
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
price_change_percentage_1h_maxNoOPTIONAL: Maximum 1h price change, in percent
price_change_percentage_1h_minNoOPTIONAL: Minimum 1h price change, in percent
price_change_percentage_5m_maxNoOPTIONAL: Maximum 5m price change, in percent
price_change_percentage_5m_minNoOPTIONAL: Minimum 5m price change, in percent. The shortest window we carry, so it is the one to reach for on 'what is moving right now'.
price_change_percentage_6h_maxNoOPTIONAL: Maximum 6h price change, in percent
price_change_percentage_6h_minNoOPTIONAL: Minimum 6h price change, in percent
price_change_percentage_24h_maxNoOPTIONAL: Maximum 24h price change, in percent
price_change_percentage_24h_minNoOPTIONAL: Minimum 24h price change, in percent. Negatives are allowed, so -20 finds pools down at least 20%.
price_change_percentage_48h_maxNoOPTIONAL: Maximum 48h price change, in percent
price_change_percentage_48h_minNoOPTIONAL: Minimum 48h price change, in percent

Output Schema

NameRequiredDescriptionDefault
queryNo
resultsNo
next_cursorNo
has_next_pageNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.9.3
    • changedInput schema / properties / created_after / description
      Previous value: -"OPTIONAL: Only pools created at or after this time: a relative offset such as '-24h' or '-7d', Unix seconds, RFC3339 or YYYY-MM-DD"New value: +"OPTIONAL: Only pools created at or after this time: a relative offset such as '-24h' or '-7d', Unix seconds, RFC3339 or YYYY-MM-DD. Without a Dev plan or higher, pools created in the last hour are left out, so a window shorter than an hour comes back empty."
  2. Changed1 schema field changedv2.9.0
    • changedInput schema / properties / cursor / description
      Previous value: -"OPTIONAL: Pagination cursor. Pass `next_cursor` from a previous response to fetch the next page. Replaces the old page number."New value: +"OPTIONAL: Pagination cursor. Pass `next_cursor` from a previous response to fetch the next page; needs an API key (a free key pages without limit). Replaces the old page number."
  3. Changed4 schema fields changedv2.8.0
    • changedInput schema / properties / order_by / enum
      Previous value: -[
      -  "volume_usd_24h",
      -  "volume_usd_7d",
      -  "volume_usd_30d",
      -  "liquidity_usd",
      -  "txns_24h",
      -  "created_at",
      -  "price_usd",
      -  "price_change_percentage_24h",
      -  "price_change_percentage_6h",
      -  "price_change_percentage_1h",
      -  "price_change_percentage_5m",
      -  "volume_usd",
      -  "transactions",
      -  "last_price_change_usd_24h",
      -  "volume_24h",
      -  "volume_7d",
      -  "volume_30d",
      -  "liquidity"
      -]New value: +[
      +  "volume_usd_24h",
      +  "volume_usd_7d",
      +  "volume_usd_30d",
      +  "liquidity_usd",
      +  "txns_24h",
      +  "created_at",
      +  "price_usd",
      +  "price_change_percentage_24h",
      +  "price_change_percentage_48h",
      +  "price_change_percentage_6h",
      +  "price_change_percentage_1h",
      +  "price_change_percentage_5m",
      +  "volume_usd",
      +  "transactions",
      +  "last_price_change_usd_24h",
      +  "volume_24h",
      +  "volume_7d",
      +  "volume_30d",
      +  "liquidity"
      +]
    • addedInput schema / properties / price_change_percentage_48h_max
      Added value: +{
      +  "description": "OPTIONAL: Maximum 48h price change, in percent",
      +  "type": "number"
      +}
    • addedInput schema / properties / price_change_percentage_48h_min
      Added value: +{
      +  "description": "OPTIONAL: Minimum 48h price change, in percent",
      +  "type": "number"
      +}
    • changedInput schema / properties / sort_by / enum
      Previous value: -[
      -  "volume_usd_24h",
      -  "volume_usd_7d",
      -  "volume_usd_30d",
      -  "liquidity_usd",
      -  "txns_24h",
      -  "created_at",
      -  "price_usd",
      -  "price_change_percentage_24h",
      -  "price_change_percentage_6h",
      -  "price_change_percentage_1h",
      -  "price_change_percentage_5m",
      -  "volume_usd",
      -  "transactions",
      -  "last_price_change_usd_24h",
      -  "volume_24h",
      -  "volume_7d",
      -  "volume_30d",
      -  "liquidity"
      -]New value: +[
      +  "volume_usd_24h",
      +  "volume_usd_7d",
      +  "volume_usd_30d",
      +  "liquidity_usd",
      +  "txns_24h",
      +  "created_at",
      +  "price_usd",
      +  "price_change_percentage_24h",
      +  "price_change_percentage_48h",
      +  "price_change_percentage_6h",
      +  "price_change_percentage_1h",
      +  "price_change_percentage_5m",
      +  "volume_usd",
      +  "transactions",
      +  "last_price_change_usd_24h",
      +  "volume_24h",
      +  "volume_7d",
      +  "volume_30d",
      +  "liquidity"
      +]
  4. Changed4 schema fields changedv2.7.1
    • changedInput schema / properties / created_after / description
      Previous value: -"OPTIONAL: Only pools created after this UNIX timestamp"New value: +"OPTIONAL: Only pools created at or after this time: a relative offset such as '-24h' or '-7d', Unix seconds, RFC3339 or YYYY-MM-DD"
    • changedInput schema / properties / created_after / type
      Previous value: -"number"New value: +"string"
    • changedInput schema / properties / created_before / description
      Previous value: -"OPTIONAL: Only pools created before this UNIX timestamp"New value: +"OPTIONAL: Only pools created at or before this time, same formats as created_after (e.g. '-1h')"
    • changedInput schema / properties / created_before / type
      Previous value: -"number"New value: +"string"
  5. Changed10 schema fields changedv2.5.0
    • changedInput schema / properties / order_by / enum
      Previous value: -[
      -  "volume_usd_24h",
      -  "volume_usd_7d",
      -  "volume_usd_30d",
      -  "liquidity_usd",
      -  "txns_24h",
      -  "created_at",
      -  "price_usd",
      -  "price_change_percentage_24h",
      -  "volume_usd",
      -  "transactions",
      -  "last_price_change_usd_24h",
      -  "volume_24h",
      -  "volume_7d",
      -  "volume_30d",
      -  "liquidity"
      -]New value: +[
      +  "volume_usd_24h",
      +  "volume_usd_7d",
      +  "volume_usd_30d",
      +  "liquidity_usd",
      +  "txns_24h",
      +  "created_at",
      +  "price_usd",
      +  "price_change_percentage_24h",
      +  "price_change_percentage_6h",
      +  "price_change_percentage_1h",
      +  "price_change_percentage_5m",
      +  "volume_usd",
      +  "transactions",
      +  "last_price_change_usd_24h",
      +  "volume_24h",
      +  "volume_7d",
      +  "volume_30d",
      +  "liquidity"
      +]
    • addedInput schema / properties / price_change_percentage_1h_max
      Added value: +{
      +  "description": "OPTIONAL: Maximum 1h price change, in percent",
      +  "type": "number"
      +}
    • addedInput schema / properties / price_change_percentage_1h_min
      Added value: +{
      +  "description": "OPTIONAL: Minimum 1h price change, in percent",
      +  "type": "number"
      +}
    • addedInput schema / properties / price_change_percentage_24h_max
      Added value: +{
      +  "description": "OPTIONAL: Maximum 24h price change, in percent",
      +  "type": "number"
      +}
    • addedInput schema / properties / price_change_percentage_24h_min
      Added value: +{
      +  "description": "OPTIONAL: Minimum 24h price change, in percent. Negatives are allowed, so -20 finds pools down at least 20%.",
      +  "type": "number"
      +}
    • addedInput schema / properties / price_change_percentage_5m_max
      Added value: +{
      +  "description": "OPTIONAL: Maximum 5m price change, in percent",
      +  "type": "number"
      +}
    • addedInput schema / properties / price_change_percentage_5m_min
      Added value: +{
      +  "description": "OPTIONAL: Minimum 5m price change, in percent. The shortest window we carry, so it is the one to reach for on 'what is moving right now'.",
      +  "type": "number"
      +}
    • addedInput schema / properties / price_change_percentage_6h_max
      Added value: +{
      +  "description": "OPTIONAL: Maximum 6h price change, in percent",
      +  "type": "number"
      +}
    • addedInput schema / properties / price_change_percentage_6h_min
      Added value: +{
      +  "description": "OPTIONAL: Minimum 6h price change, in percent",
      +  "type": "number"
      +}
    • changedInput schema / properties / sort_by / enum
      Previous value: -[
      -  "volume_usd_24h",
      -  "volume_usd_7d",
      -  "volume_usd_30d",
      -  "liquidity_usd",
      -  "txns_24h",
      -  "created_at",
      -  "price_usd",
      -  "price_change_percentage_24h",
      -  "volume_usd",
      -  "transactions",
      -  "last_price_change_usd_24h",
      -  "volume_24h",
      -  "volume_7d",
      -  "volume_30d",
      -  "liquidity"
      -]New value: +[
      +  "volume_usd_24h",
      +  "volume_usd_7d",
      +  "volume_usd_30d",
      +  "liquidity_usd",
      +  "txns_24h",
      +  "created_at",
      +  "price_usd",
      +  "price_change_percentage_24h",
      +  "price_change_percentage_6h",
      +  "price_change_percentage_1h",
      +  "price_change_percentage_5m",
      +  "volume_usd",
      +  "transactions",
      +  "last_price_change_usd_24h",
      +  "volume_24h",
      +  "volume_7d",
      +  "volume_30d",
      +  "liquidity"
      +]
  6. Changed4 schema fields changedv2.3.2
    • changedInput schema / properties / order_by / description
      Previous value: -"OPTIONAL (deprecated alias of sort_by): Field to sort by"New value: +"OPTIONAL: 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."
    • changedInput schema / properties / sort / description
      Previous value: -"OPTIONAL (deprecated alias of sort_dir): Sort direction"New value: +"OPTIONAL: 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."
    • changedInput schema / properties / sort_by / description
      Previous value: -"OPTIONAL (preferred): Field to sort by (default: 'volume_usd_24h'). Prefer the canonical *_24h names; short legacy names are still accepted."New value: +"OPTIONAL (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."
    • changedInput schema / properties / sort_dir / description
      Previous value: -"OPTIONAL (preferred): Sort direction (default: 'desc')"New value: +"OPTIONAL (preferred): Sort direction (default: 'desc'). The REST API calls this parameter sort."
  7. Changed9 schema fields changedv1.0.2
    • addedInput schema / properties / cursor
      Added value: +{
      +  "description": "OPTIONAL: Pagination cursor. Pass `next_cursor` from a previous response to fetch the next page. Replaces the old page number.",
      +  "type": "string"
      +}
    • changedInput schema / properties / order_by / enum
      Previous value: -[
      -  "volume_24h",
      -  "volume_7d",
      -  "volume_30d",
      -  "liquidity",
      -  "txns_24h",
      -  "created_at"
      -]New value: +[
      +  "volume_usd_24h",
      +  "volume_usd_7d",
      +  "volume_usd_30d",
      +  "liquidity_usd",
      +  "txns_24h",
      +  "created_at",
      +  "price_usd",
      +  "price_change_percentage_24h",
      +  "volume_usd",
      +  "transactions",
      +  "last_price_change_usd_24h",
      +  "volume_24h",
      +  "volume_7d",
      +  "volume_30d",
      +  "liquidity"
      +]
    • removedInput schema / properties / page
      Removed value: -{
      -  "default": 1,
      -  "description": "OPTIONAL: Page number for pagination (default: 1, 1-indexed)",
      -  "type": "number"
      -}
    • changedInput schema / properties / sort_by / description
      Previous value: -"OPTIONAL (preferred): Field to sort by (default: 'volume_24h')"New value: +"OPTIONAL (preferred): Field to sort by (default: 'volume_usd_24h'). Prefer the canonical *_24h names; short legacy names are still accepted."
    • changedInput schema / properties / sort_by / enum
      Previous value: -[
      -  "volume_24h",
      -  "volume_7d",
      -  "volume_30d",
      -  "liquidity",
      -  "txns_24h",
      -  "created_at"
      -]New value: +[
      +  "volume_usd_24h",
      +  "volume_usd_7d",
      +  "volume_usd_30d",
      +  "liquidity_usd",
      +  "txns_24h",
      +  "created_at",
      +  "price_usd",
      +  "price_change_percentage_24h",
      +  "volume_usd",
      +  "transactions",
      +  "last_price_change_usd_24h",
      +  "volume_24h",
      +  "volume_7d",
      +  "volume_30d",
      +  "liquidity"
      +]
    • addedOutput schema / properties / has_next_page
      Added value: +{
      +  "type": "boolean"
      +}
    • addedOutput schema / properties / next_cursor
      Added value: +{
      +  "type": [
      +    "string",
      +    "null"
      +  ]
      +}
    • removedOutput schema / properties / page_info
      Removed value: -{
      -  "additionalProperties": true,
      -  "properties": {
      -    "limit": {
      -      "description": "Items per page in the request.",
      -      "type": "number"
      -    },
      -    "page": {
      -      "description": "Current page number (1-indexed).",
      -      "type": "number"
      -    },
      -    "total_items": {
      -      "description": "Total number of items across all pages.",
      -      "type": "number"
      -    },
      -    "total_pages": {
      -      "description": "Total number of pages available.",
      -      "type": "number"
      -    }
      -  },
      -  "type": "object"
      -}
    • addedOutput schema / properties / query
      Added value: +{
      +  "additionalProperties": {},
      +  "type": "object"
      +}
  8. Addedv1.0.1

TDQS

A4.8/5.0
Behavior5/5

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

Goes well beyond the readOnly/idempotent annotations by disclosing the auth model (first page works without a key, cursor paging requires one), the plan gating that silently drops pools created in the last hour, and the AND-combination semantics of the optional filters. The plan-tier exclusion is exactly the kind of silent filtering an agent must know about to avoid reporting a false negative.

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?

Front-loads purpose, then response shape, then the sibling choice, then caveats — a sensible order with no filler sentences. It loses a point for repetition: the API-key-paging requirement appears in both the description and three schema fields, and the plan-tier caveat is restated inside created_after.

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 27 parameters, a required rationale field, an output schema, and existing annotations, this is a complex tool that still gets adequate coverage. Purpose, routing, auth prerequisites, plan limits, filter combination logic, and date formats are all addressed, and return values are delegated to the output schema as appropriate.

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?

Schema coverage is 100%, so the baseline is 3, but the description adds semantics the schema does not state: all optional filters are AND-combined, and created_after/created_before accept relative offsets, Unix seconds, RFC3339 or YYYY-MM-DD. Remaining content (limit default 50/max 100, sort_by default, alias names) repeats the schema rather than adding to it.

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?

States a specific verb and resource (get pools on one network) plus the distinguishing mechanism (numeric threshold filtering) and the response envelope ('results', has_next_page, next_cursor). It explicitly contrasts itself with getNetworkPools, so an agent can route between the two without opening either schema.

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?

Gives an explicit selection rule ('choose this over getNetworkPools when the user gives numeric constraints or a time window') and three concrete user-utterance examples mapping to parameter combinations. It also states the negative case: a created_after window shorter than an hour returns empty without a Dev plan.

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