DexPaprika (CoinPaprika)

Official

Overview Schema Source Related Servers Discussions Admin

getTopTokens

Read-onlyIdempotent

Identify top tokens on any network by volume, liquidity, transactions, FDV, or price change. Sort and paginate results to spot market leaders and gainers for analysis.

Instructions

Get the top tokens on one network ranked by volume, liquidity, transactions, FDV, or 24h price change, returned under 'results' with has_next_page and next_cursor. Read-only and keyless. Use for 'top gainers on Solana', 'highest-volume tokens on Base', or 'biggest tokens by FDV on ethereum'. For arbitrary numeric filters or a time window use filterNetworkTokens instead. Params: network (required slug); limit (default 50, max 100); cursor (pass previous next_cursor to page); sort_by (default 'volume_usd_24h', alias order_by), noting that ranking by raw price is unsupported and silently falls back to volume; sort_dir asc/desc (default 'desc', alias sort).

Input Schema

TableJSON Schema

Name	Required	Description
`sort`	No	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.
`limit`	No	OPTIONAL: Number of items per page (default: 50, max: 100)
`cursor`	No	OPTIONAL: Pagination cursor. Pass `next_cursor` from a previous response to fetch the next page. Replaces the old page number.
`network`	Yes	REQUIRED: Network ID from getNetworks (e.g., 'ethereum', 'solana')
`sort_by`	No	OPTIONAL (preferred): Field to sort by (default: 'volume_usd_24h'). Prefer the canonical names; short legacy names are still accepted. The REST API calls this parameter order_by.
`order_by`	No	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.
`sort_dir`	No	OPTIONAL (preferred): Sort direction (default: 'desc'). The REST API calls this parameter sort.
`rationale`	Yes	REQUIRED. 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

Name	Required	Description	Default
`query`	No
`results`	No
`next_cursor`	No
`has_next_page`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedv2.3.2Jul 30, 2026

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 names; short legacy names are still accepted."New value: +"OPTIONAL (preferred): Field to sort by (default: 'volume_usd_24h'). Prefer the canonical 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."

Changed11 schema fields changedv1.0.2Jul 29, 2026

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",
-  "price_usd",
-  "liquidity_usd",
-  "txns",
-  "price_change"
-]New value: +[
+  "volume_usd_24h",
+  "volume_usd_7d",
+  "volume_usd_30d",
+  "liquidity_usd",
+  "txns_24h",
+  "fdv_usd",
+  "created_at",
+  "price_change_percentage_24h",
+  "volume_24h",
+  "volume_7d",
+  "volume_30d",
+  "txns",
+  "price_change",
+  "fdv",
+  "price_usd"
+]

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 names; short legacy names are still accepted."

changedInput schema / properties / sort_by / enum

Previous value: -[
-  "volume_24h",
-  "price_usd",
-  "liquidity_usd",
-  "txns",
-  "price_change"
-]New value: +[
+  "volume_usd_24h",
+  "volume_usd_7d",
+  "volume_usd_30d",
+  "liquidity_usd",
+  "txns_24h",
+  "fdv_usd",
+  "created_at",
+  "price_change_percentage_24h",
+  "volume_24h",
+  "volume_7d",
+  "volume_30d",
+  "txns",
+  "price_change",
+  "fdv",
+  "price_usd"
+]

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"
+}

addedOutput schema / properties / results

Added value: +{
+  "items": {
+    "additionalProperties": true,
+    "properties": {
+      "added_at": {
+        "description": "ISO 8601 timestamp when DexPaprika first indexed this token.",
+        "type": "string"
+      },
+      "chain": {
+        "type": "string"
+      },
+      "decimals": {
+        "type": "number"
+      },
+      "fdv": {
+        "description": "Fully-diluted valuation in USD.",
+        "type": [
+          "number",
+          "null"
+        ]
+      },
+      "id": {
+        "description": "Token contract address (chain-canonical form).",
+        "type": "string"
+      },
+      "name": {
+        "type": "string"
+      },
+      "symbol": {
+        "type": "string"
+      }
+    },
+    "type": "object"
+  },
+  "type": "array"
+}

removedOutput schema / properties / tokens

Removed value: -{
-  "items": {
-    "additionalProperties": true,
-    "properties": {
-      "added_at": {
-        "description": "ISO 8601 timestamp when DexPaprika first indexed this token.",
-        "type": "string"
-      },
-      "chain": {
-        "type": "string"
-      },
-      "decimals": {
-        "type": "number"
-      },
-      "fdv": {
-        "description": "Fully-diluted valuation in USD.",
-        "type": [
-          "number",
-          "null"
-        ]
-      },
-      "id": {
-        "description": "Token contract address (chain-canonical form).",
-        "type": "string"
-      },
-      "name": {
-        "type": "string"
-      },
-      "symbol": {
-        "type": "string"
-      }
-    },
-    "type": "object"
-  },
-  "type": "array"
-}

Addedv1.0.1Jun 24, 2026

TDQS

A5/5.0

Behavior5/5

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

Expands beyond annotations: notes keyless access, pagination response format, and the critical caveat that sorting by raw price silently falls back to volume. Annotations already cover idempotent/read-only; description adds operational detail.

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?

Concise yet comprehensive: first sentence states purpose, second gives usage guidance, third details parameters. No extraneous text; 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?

Covers all aspects: purpose, parameters, pagination, caveats, and alternative tool. Output schema exists so return format is adequately summarized. No gaps.

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 adds value: explains aliases (sort->sort_dir, order_by->sort_by), default/max for limit, cursor usage, and the price sorting fallback. Schema alone doesn't provide this context.

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 the tool retrieves top tokens ranked by various metrics (volume, liquidity, etc.) and gives concrete examples ('top gainers on Solana'). Distinguishes from sibling filterNetworkTokens.

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 says when to use (top tokens by specific metrics) and when not to (arbitrary numeric filters or time window), directing to filterNetworkTokens. Also mentions read-only and keyless.

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

Deploy Server