DexPaprika

getNetworks

Read-onlyIdempotent

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

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

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 changedOct 23, 2026

removedOutput schema / properties / networks / items / additionalProperties
```
Removed value: -true
```

addedOutput schema / properties / networks / items / anyOf

Added value: +[
+  {
+    "additionalProperties": true,
+    "properties": {
+      "display_name": {
+        "description": "Human-readable network name (e.g. 'Ethereum').",
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "id": {
+        "description": "Network slug for use in other endpoints (e.g. 'ethereum').",
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "pools_count": {
+        "description": "Number of indexed pools on this network.",
+        "type": [
+          "number",
+          "null"
+        ]
+      },
+      "txns_24h": {
+        "description": "Total transactions in the last 24h on this network.",
+        "type": [
+          "number",
+          "null"
+        ]
+      },
+      "volume_usd_24h": {
+        "description": "Total 24h trading volume across all pools on this network, USD.",
+        "type": [
+          "number",
+          "null"
+        ]
+      }
+    },
+    "type": "object"
+  },
+  {
+    "type": "null"
+  }
+]

removedOutput schema / properties / networks / items / properties

Removed value: -{
-  "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"
-  }
-}

removedOutput schema / properties / networks / items / type
```
Removed value: -"object"
```

Changed1 schema field changedSep 2, 2026

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

First observedJul 28, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Annotations already declare readOnly/idempotent/openWorld, but the description adds genuinely new context: keyless access, no pagination, no sorting, entire array returned in one shot. That tells the agent it cannot page or narrow results, which annotations alone would not convey.

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?

Front-loaded with what the tool returns, then where to go next, then use cases, then the getStats exclusion. Parenthetical asides and quoted query examples are dense with signal, not 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?

An output schema exists, so return-value detail is not required; the description still summarizes the row shape. Combined with keyless/no-pagination behavior and the slug-discovery workflow, nothing an agent needs before calling 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% and the single rationale parameter is fully documented in the schema, so the baseline is 3. The description still earns credit by asserting the tool "takes no parameters beyond a short rationale", implicitly confirming that no filter/sort/pagination params exist — useful for shaping expectations beyond the schema.

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 ("List every blockchain network DexPaprika indexes") and immediately names the fields each row carries (slug, 24h volume, tx count, pool count). This is clearly separable from getStats (platform totals) and getCapabilities, both named in the text.

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 framing ("Start here (or getCapabilities) to get the exact network slug that nearly every other tool requires") plus three representative user phrasings. It also names the exclusion: "For platform-wide totals rather than a per-network list use getStats."

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

All DexPaprika tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?