DexPaprika (CoinPaprika)

Official

Overview Schema Source Related Servers Discussions Admin

getNetworks

Read-onlyIdempotent

List all supported blockchain networks with 24h volume, transaction counts, and pool counts to identify the exact network slug required by other DexPaprika tools.

Instructions

List every blockchain network DexPaprika indexes, each row carrying its network id (slug), 24h volume, transaction count, and pool count. Read-only and keyless. Start here (or getCapabilities) to get the exact network slug that nearly every other tool requires as its 'network' argument. Use for 'which chains do you support?', 'is Base/Solana/Arbitrum covered?', or 'what is the slug for Polygon?'. Returns the full array with no pagination or sorting; takes no parameters beyond a short rationale. For platform-wide totals rather than a per-network list use getStats.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`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
`networks`	Yes	All supported blockchain networks with current 24h volume + indexing stats.

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedv1.0.1Jun 24, 2026

addedInput schema / additionalProperties
```
Added value: +false
```

addedInput schema / properties / rationale

Added value: +{
+  "description": "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.",
+  "maxLength": 500,
+  "minLength": 20,
+  "type": "string"
+}

addedInput schema / required
```
Added value: +[
+  "rationale"
+]
```

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": true,
+  "properties": {
+    "networks": {
+      "description": "All supported blockchain networks with current 24h volume + indexing stats.",
+      "items": {
+        "additionalProperties": true,
+        "properties": {
+          "display_name": {
+            "description": "Human-readable network name (e.g. 'Ethereum').",
+            "type": "string"
+          },
+          "id": {
+            "description": "Network slug for use in other endpoints (e.g. 'ethereum').",
+            "type": "string"
+          },
+          "pools_count": {
+            "description": "Number of indexed pools on this network.",
+            "type": "number"
+          },
+          "txns_24h": {
+            "description": "Total transactions in the last 24h on this network.",
+            "type": "number"
+          },
+          "volume_usd_24h": {
+            "description": "Total 24h trading volume across all pools on this network, USD.",
+            "type": "number"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "networks"
+  ],
+  "type": "object"
+}

Changed1 schema field changedv1.0.0Jan 3, 2026
- removedInput schema / additionalProperties
```
Removed value: -false
```
First observedAug 15, 2025

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare readOnly, openWorld, idempotent, and non-destructive hints, and the description adds useful behavioral details beyond those: it states 'keyless' access, 'returns the full array with no pagination or sorting,' and that no parameters besides rationale are accepted. This goes beyond the structured annotations without contradicting them.

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 packed with high-value information—purpose, return fields, keyless access, usage examples, and a cross-reference to getStats—while remaining compact. Every sentence contributes to either selection, invocation, or interpretation of the tool; there is no filler.

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?

For a simple list tool with a single required parameter and an output schema, the description fully covers what the agent needs: what the result contains, how to obtain the network slug for downstream calls, pagination/sorting behavior, and the alternative for platform-wide statistics. Nothing critical is missing.

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?

The schema already documents the single rationale parameter with a clear description (coverage 100%), and the description reiterates 'takes no parameters beyond a short rationale.' This adds marginal clarity but does not materially extend what the schema provides, so baseline 3 is appropriate.

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 begins with a specific verb and resource: 'List every blockchain network DexPaprika indexes,' and enumerates the exact data fields (slug, volume, transaction count, pool count). It distinguishes itself from getStats and getCapabilities, so an agent can clearly tell what this tool does and what it does not.

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?

Gives explicit when-to-use guidance: 'Start here (or getCapabilities) to get the exact network slug that nearly every other tool requires' and provides concrete example queries like 'is Base/Solana/Arbitrum covered?'. It also names the alternative getStats for platform-wide totals, offering both inclusion and exclusion criteria.

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

Deploy Server