DexPaprika

search

Read-onlyIdempotent

Search across ALL networks at once for tokens, pools, and DEXes by name, symbol, or address, returning three arrays: 'tokens', 'pools', and 'dexes'. Read-only and keyless. This is the cross-chain entry point when you do not yet know which network something lives on; once you have a network slug from the results, switch to the network-scoped tools. Use for 'find PEPE', 'what is the address for USDC', or 'which chain is this token on?'. Several words work: 'WETH USDC' returns the pools pairing both, and a network name ('brett base') narrows results to that chain. No matches returns empty arrays, not an error. Params: query (required; a name, symbol, or contract address, e.g. 'uniswap', 'bitcoin', or '0x...'); limit (optional, caps results per category, applied client-side).

Input Schema

TableJSON Schema

Name	Required	Description
`limit`	No	OPTIONAL: Cap items returned per category (tokens, pools, dexes). Upstream returns all matches by default; this client-side slice keeps payloads small for agents. Applies independently to each category.
`query`	Yes	REQUIRED: Search term (e.g., 'uniswap', 'bitcoin', 'ethereum', 'WETH USDC', or a token address).
`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
`dexes`	Yes
`pools`	Yes
`tokens`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 1, 2026

changedInput schema / properties / query / description

Previous value: -"REQUIRED: Search term (e.g., 'uniswap', 'bitcoin', 'ethereum', or a token address)."New value: +"REQUIRED: Search term (e.g., 'uniswap', 'bitcoin', 'ethereum', 'WETH USDC', or a token address)."

Changed1 schema field changedSep 2, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": true,
+  "properties": {
+    "dexes": {
+      "items": {
+        "additionalProperties": true,
+        "properties": {
+          "chain": {
+            "type": "string"
+          },
+          "dex_id": {
+            "type": "string"
+          },
+          "dex_name": {
+            "type": "string"
+          },
+          "display_name": {
+            "type": "string"
+          },
+          "id": {
+            "type": "string"
+          },
+          "network_id": {
+            "type": "string"
+          },
+          "pools_count": {
+            "type": "number"
+          },
+          "protocol": {
+            "type": "string"
+          },
+          "txns_24h": {
+            "type": "number"
+          },
+          "volume_usd_24h": {
+            "type": "number"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "pools": {
+      "items": {
+        "additionalProperties": true,
+        "properties": {
+          "chain": {
+            "description": "Network slug (e.g. 'ethereum'). Note: also exposed as 'network' on some endpoints.",
+            "type": "string"
+          },
+          "created_at": {
+            "description": "ISO 8601 pool-creation timestamp.",
+            "type": "string"
+          },
+          "created_at_block_number": {
+            "type": "number"
+          },
+          "dex_id": {
+            "type": "string"
+          },
+          "dex_name": {
+            "type": "string"
+          },
+          "fee": {
+            "description": "Pool fee (units depend on DEX; null for some DEXes).",
+            "type": [
+              "number",
+              "null"
+            ]
+          },
+          "id": {
+            "description": "Pool contract address.",
+            "type": "string"
+          },
+          "last_price": {
+            "type": [
+              "number",
+              "null"
+            ]
+          },
+          "last_price_usd": {
+            "type": [
+              "number",
+              "null"
+            ]
+          },
+          "tokens": {
+            "items": {
+              "$ref": "#/properties/tokens/items"
+            },
+            "type": "array"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "tokens": {
+      "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"
+    }
+  },
+  "required": [
+    "tokens",
+    "pools",
+    "dexes"
+  ],
+  "type": "object"
+}

First observedJul 28, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Annotations already cover read-only/idempotent/non-destructive, but the description adds real value: keyless operation, empty-array-on-no-match instead of an error, and multi-word query behavior ('WETH USDC'). It doesn't discuss result ordering or pagination, keeping it short of a 5.

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, scope, return shape, then usage, then params. Slightly long due to multiple examples, but each sentence (empty arrays, multi-word behavior) carries information an agent needs.

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?

Output schema exists, so return values needn't be explained, yet the description still notes the three arrays and no-match behavior. Scope, usage, and the sibling handoff are all present — nothing an agent needs to call this correctly 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 semantics beyond the schema — multi-word queries, network-name narrowing ('brett base'), and that limit is a client-side slice per category. Params are well covered.

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 (search) plus the three resources searched (tokens, pools, dexes) and the scope (ALL networks). It explicitly distinguishes itself from the network-scoped siblings, so an agent can pick it without opening schemas.

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 ('cross-chain entry point when you do not yet know which network') and a handoff rule ('once you have a network slug, switch to the network-scoped tools'), plus concrete example queries.

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?