Skip to main content
Glama
coinpaprika

DexPaprika (CoinPaprika)

Official
by coinpaprika
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

getTopTokens

Read-onlyIdempotent

Rank tokens on a chosen network by volume, liquidity, transactions, FDV, or 24h price change to surface gainers and high-volume assets.

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. The first page works without an API key; paging with cursor needs a key (a free key pages without limit). 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

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 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.

Output Schema

NameRequiredDescriptionDefault
queryNo
resultsNo
next_cursorNo
has_next_pageNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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."
  2. 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 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."
  3. Changed11 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",
-  "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"
-}
  4. Addedv1.0.1

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already declare read-only/idempotent, but the description adds real operational context beyond them: the first page works without an API key while cursor paging requires one, a free key pages without limit, and ranking by raw price silently falls back to volume. These are exactly the behavioral traits an agent cannot infer from 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?

Front-loaded with purpose, output shape, auth caveat, and examples before the parameter block, and every clause carries information. It is dense and slightly run-on in the trailing params sentence, which keeps it off a 5.

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 a full output schema and rich annotations, the description fills the remaining gaps: auth/paging behavior, the sort fallback, and sibling routing. Nothing an agent needs to call this correctly at 8 params is missing.

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 value the schema does not: it flags the alias pairs (order_by/sort_by, sort/sort_dir) in the same breath as defaults, and warns that sorting by raw price is unsupported and silently degrades to volume — a trap the enum alone does not expose.

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 the top tokens on one network') plus the exact ranking dimensions, the response envelope ('results', has_next_page, next_cursor), and explicitly distinguishes itself from filterNetworkTokens. An agent can select it without opening the 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?

Provides concrete trigger examples ('top gainers on Solana', 'highest-volume tokens on Base') and names the alternative with the condition that selects it: 'For arbitrary numeric filters or a time window use filterNetworkTokens instead.' When-to-use and when-not-to-use are both explicit.

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

Deploy Server

Other Tools