Skip to main content
Glama
coinpaprika

DexPaprika (CoinPaprika)

Official

getTokenPools

Read-onlyIdempotent

Retrieve liquidity pools that include a specific token across multiple blockchains. Filter by paired token, sort by volume or price, and paginate results for tailored DeFi analysis.

Instructions

Get liquidity pools containing a token. REQUIRED: network, token_address. OPTIONAL: page, limit, sort_dir/sort, sort_by/order_by, inversed/reorder, paired_token_address/address.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
networkYesREQUIRED: Network ID from getNetworks (e.g., 'ethereum', 'solana')
token_addressYesREQUIRED: Token contract address
pageNoOPTIONAL: Page number for pagination (default: 1, 1-indexed)
limitNoOPTIONAL: Number of items per page (default: 10, max: 100)
sort_dirNoOPTIONAL (preferred): Sort direction (default: 'desc')
sortNoOPTIONAL (deprecated alias of sort_dir): Sort direction
sort_byNoOPTIONAL (preferred): Field to sort by (default: 'volume_usd')
order_byNoOPTIONAL (deprecated alias of sort_by): Field to sort by
inversedNoOPTIONAL (preferred): Flip the pool's pair perspective so the specified token becomes primary
reorderNoOPTIONAL (deprecated alias of inversed): Reorder the pool
paired_token_addressNoOPTIONAL (preferred): Filter pools that also contain this token address
addressNoOPTIONAL (deprecated alias of paired_token_address): Additional token address filter
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
Behavior4/5

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

Annotations already declare read-only, non-destructive, idempotent, and open-world behavior. The description adds value by clarifying parameter groupings, preferred versus deprecated aliases, and the overall purpose, 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single sentence for purpose followed by a compact list of required and optional parameters. No wasted words, and the key information is front-loaded.

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?

Given the 13 parameters, 3 required, and existence of an output schema, the description covers all necessary context: parameter grouping, alias preferences, and validation constraints like defaults and max values. The agent has enough information to use the tool correctly.

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%, baseline is 3. The description adds meaning by grouping parameters (REQUIRED, OPTIONAL) and noting preferred aliases (e.g., sort_dir over sort), which helps the agent choose correct parameters.

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 clearly states 'Get liquidity pools containing a token.' It uses a specific verb ('Get') and resource ('liquidity pools'), and the token focus distinguishes it from sibling tools like getNetworkPools or getDexPools.

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?

The description labels parameters as REQUIRED and OPTIONAL, providing clear usage context. However, it does not explicitly mention when to use this tool versus alternatives like getNetworkPools or getDexPools, nor does it specify when not to use it.

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