Skip to main content
Glama

DexPaprika

by com.dexpaprika.mcp

filterNetworkTokens

Read-onlyIdempotent

Get tokens on one network matching numeric thresholds, returned under 'results' with has_next_page and next_cursor. Read-only and keyless. Choose this over getTopTokens when the user gives numeric constraints or a time window. Use for 'tokens with FDV over $10M on Base', 'newly created tokens today', or 'low-liquidity high-volume tokens'. Optional filters (AND-combined): volume_24h_min/max, liquidity_usd_min/max, fdv_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: 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.
fdv_maxNoOPTIONAL: Maximum FDV in USD
fdv_minNoOPTIONAL: Minimum FDV in USD
networkYesREQUIRED: Network ID from getNetworks
sort_byNoOPTIONAL: Sort field. Defaults to 'volume_usd_24h'. Prefer the canonical 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: Sort direction (asc/desc). Canonical parameter name. Defaults to 'desc' if neither sort_dir nor sort is provided. 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 transactions in 24h
created_afterNoOPTIONAL: Only tokens created after this UNIX timestamp
created_beforeNoOPTIONAL: Only tokens 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 token liquidity in USD
liquidity_usd_minNoOPTIONAL: Minimum token liquidity in USD

TDQS

A4.8/5.0
Behavior5/5

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

Beyond the annotations (readOnlyHint, idempotentHint, etc.), the description states 'Read-only and keyless', disclosing authentication requirements. It also reveals response shape (results, has_next_page, next_cursor) and clarifies that filters are AND-combined. This adds significant behavioral context without contradicting annotations.

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 dense but well-structured, starting with purpose then moving to usage, filters, and parameters. It is slightly long due to listing many filters, but every sentence contributes operational detail—no filler or 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 17 parameters and no output schema, the description carries a heavy burden. It fully covers the response envelope, pagination mechanics, filter semantics, aliases, and concrete example use cases, making the tool self-explanatory for an agent.

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 baseline is 3. The description adds value by explaining AND-combination semantics, alias relationships (sort_by/order_by, sort_dir/sort), and defaults (limit 50, sort default volume_usd_24h). This goes beyond what the schema already specifies.

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 opens with a specific verb and resource: 'Get tokens on one network matching numeric thresholds', and explicitly names response fields ('results', has_next_page, next_cursor). It distinguishes itself from the sibling tool getTopTokens, making its purpose immediately clear.

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?

The description provides explicit usage guidance: 'Choose this over getTopTokens when the user gives numeric constraints or a time window' and gives concrete example queries ('tokens with FDV over $10M on Base'). This goes beyond implied usage and clearly delineates when to use this tool versus alternatives.

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

All DexPaprika toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.4/5.0
Disambiguation5/5

Every tool has a clearly distinct purpose: network listings, DEX listings, pool discovery, pool snapshots, OHLCV, transactions, token details, multi-price, token pools, search, stats, and feedback. Potential overlaps like getTopTokens vs filterNetworkTokens are explicitly disambiguated in descriptions.

Naming Consistency4/5

Mostly follows camelCase verb-first pattern (getNetworks, getPoolDetails, getTokenMultiPrices). However, the pair filterNetworkTokens and getNetworkPoolsFilter are inconsistently structured; the latter should logically be filterNetworkPools for full consistency.

Tool Count4/5

At 17 tools, it slightly exceeds the ideal 3-15 range, but each tool covers a distinct data operation for a comprehensive DEX-market API. The count feels justified given the breadth of features, though it is on the heavier side.

Completeness4/5

The domain of read-only DEX analytics is well covered: networks, DEXes, pools, tokens, search, stats, and per-pool history. Minor gaps exist, such as no direct token price history endpoint, but pool OHLCV and token details cover most needs.

Resources