Skip to main content
Glama
Sign In

DexPaprika

by com.dexpaprika.mcp
OverviewDiscussionsAdmin

getStats

Read-onlyIdempotent

Get platform-wide totals for DexPaprika: the number of networks, DEXes, pools, and tokens indexed, returned as a single summary object. Read-only and keyless. Use for 'how much data do you cover?', 'how many chains or pools total?', or a one-line coverage summary. These are ecosystem-wide counts, not per-network figures; use getNetworks for the per-chain breakdown, or getCapabilities for onboarding docs. Takes no parameters beyond a short rationale.

Input Schema

NameRequiredDescriptionDefault
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
poolsYesTotal pools indexed across all chains.
chainsYesTotal chains indexed.
tokensYesTotal tokens indexed.
factoriesYesTotal DEX factory contracts indexed.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • changedOutput schema / properties / chains / type
      Previous value: -"number"New value: +[
+  "number",
+  "null"
+]
    • changedOutput schema / properties / factories / type
      Previous value: -"number"New value: +[
+  "number",
+  "null"
+]
    • changedOutput schema / properties / pools / type
      Previous value: -"number"New value: +[
+  "number",
+  "null"
+]
    • changedOutput schema / properties / tokens / type
      Previous value: -"number"New value: +[
+  "number",
+  "null"
+]
  2. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": true,
+  "properties": {
+    "chains": {
+      "description": "Total chains indexed.",
+      "type": "number"
+    },
+    "factories": {
+      "description": "Total DEX factory contracts indexed.",
+      "type": "number"
+    },
+    "pools": {
+      "description": "Total pools indexed across all chains.",
+      "type": "number"
+    },
+    "tokens": {
+      "description": "Total tokens indexed.",
+      "type": "number"
+    }
+  },
+  "required": [
+    "chains",
+    "factories",
+    "pools",
+    "tokens"
+  ],
+  "type": "object"
+}
  3. First observed

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description adds 'keyless' access and the fact that results come back as a single summary object rather than a collection. It does not cover rate limits or refresh cadence, so it is strong but not exhaustive.

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-loads the purpose, then usage examples, then the sibling disambiguation. Four sentences, each carrying distinct information with no restatement of the name.

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 is present so return shape need not be explained, and the description covers scope, safety posture, access requirements, and alternatives. Nothing needed to invoke this zero-filter tool 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 rationale parameter is fully documented in the schema itself; the description's note that the tool 'takes no parameters beyond a short rationale' usefully confirms no filter arguments exist. That is additive but thin 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 ('Get platform-wide totals ... number of networks, DEXes, pools, and tokens indexed') and explicitly scopes it as ecosystem-wide rather than per-chain. This directly separates it from getNetworks, which the description names.

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 example queries ('how much data do you cover?', 'how many chains or pools total?') plus explicit routing to getNetworks for per-chain breakdowns and getCapabilities for onboarding docs. Both the when-to-use and the alternatives are spelled out.

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

All DexPaprika toolsInspect
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