Skip to main content
Glama
coinpaprika

DexPaprika (CoinPaprika)

Official

getPoolDetails

Read-onlyIdempotent

Get detailed information about a decentralized exchange pool by providing network and pool address. Optionally invert the price ratio.

Instructions

Get detailed info about a pool. REQUIRED: network, pool_address. OPTIONAL: inversed.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
networkYesREQUIRED: Network ID from getNetworks (e.g., 'ethereum', 'solana')
pool_addressYesREQUIRED: Pool address or identifier (e.g., '0x88e6a0c2ddd26feeb64f039a2c41296fcb3f5640')
inversedNoOPTIONAL: Whether to invert the price ratio (default: false)
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
idNo
chainNo
factory_idNo
dex_idNo
dex_nameNo
created_atNo
created_at_block_numberNo
feeNo
tokensNo
token_reservesNo
last_priceNo
last_price_usdNo
price_timeNo
price_statsNo
Behavior3/5

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

Annotations fully declare readOnlyHint=true, destructiveHint=false, idempotentHint=true, openWorldHint=true. The description adds no additional behavioral context beyond 'Get detailed info', so it is adequate but does not enhance transparency beyond the 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 a single sentence plus a brief list of required/optional parameters. It is concise and front-loaded, but the list format repeats schema information without adding value.

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

Completeness4/5

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

Given the comprehensive schema (100% coverage), full annotations, and presence of an output schema, the minimal description is sufficient for a basic read-only detail fetch. However, it could briefly hint at what 'detailed info' contains (e.g., liquidity, volume).

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so baseline is 3. The description restates required/optional but does not add new meaning or examples beyond what the schema already provides.

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 the verb 'Get' and the resource 'detailed info about a pool', making it distinct from sibling tools that list pools or provide OHLCV data.

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?

While the description lists required and optional parameters, it does not provide explicit guidance on when to use this tool versus alternatives like getNetworkPools. The context is implied by the name but not stated.

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