DexPaprika

getCapabilities

Read-onlyIdempotent

Get the static agent onboarding guide for this server: supported workflows, network name synonyms (mapping words like 'eth' to the canonical slug 'ethereum'), recommended call sequences, and common pitfalls. Read-only and keyless. Read it once at the start of a session before your first query, or when asked 'how do I use this API?', 'what order should I call things in?', or 'which slug maps to eth?'. This returns onboarding docs, not live market data; for the actual list of network slugs use getNetworks, and for coverage totals use getStats. Takes no parameters beyond a short rationale.

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
`stats`	Yes
`server`	Yes
`workflows`	Yes	Named tool sequences for common agent tasks.
`agent_skills`	Yes
`documentation`	Yes
`common_pitfalls`	Yes	Known edge cases agents should be aware of.
`network_synonyms`	Yes	Canonical network id -> common alternates an agent might try.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 2, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": true,
+  "properties": {
+    "agent_skills": {
+      "type": "string"
+    },
+    "common_pitfalls": {
+      "description": "Known edge cases agents should be aware of.",
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "documentation": {
+      "type": "string"
+    },
+    "network_synonyms": {
+      "additionalProperties": {
+        "items": {
+          "type": "string"
+        },
+        "type": "array"
+      },
+      "description": "Canonical network id -> common alternates an agent might try.",
+      "type": "object"
+    },
+    "server": {
+      "additionalProperties": true,
+      "properties": {
+        "name": {
+          "type": "string"
+        },
+        "version": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "name",
+        "version"
+      ],
+      "type": "object"
+    },
+    "stats": {
+      "additionalProperties": true,
+      "properties": {
+        "console_url": {
+          "type": "string"
+        },
+        "docs_url": {
+          "type": "string"
+        },
+        "free_key_credits_per_month": {
+          "type": "number"
+        },
+        "free_key_requests_per_minute": {
+          "type": "number"
+        },
+        "free_tier": {
+          "type": "boolean"
+        },
+        "free_tier_credits_per_month": {
+          "type": "number"
+        },
+        "free_tier_max_data_delay_seconds": {
+          "type": "number"
+        },
+        "free_tier_requests_per_minute": {
+          "type": "number"
+        },
+        "key_required_to_start": {
+          "type": "boolean"
+        },
+        "networks": {
+          "type": "number"
+        },
+        "pools_approx": {
+          "type": "number"
+        },
+        "pricing_url": {
+          "type": "string"
+        },
+        "tokens_approx": {
+          "type": "number"
+        }
+      },
+      "required": [
+        "networks",
+        "tokens_approx",
+        "pools_approx",
+        "free_tier",
+        "key_required_to_start"
+      ],
+      "type": "object"
+    },
+    "workflows": {
+      "additionalProperties": {
+        "items": {
+          "type": "string"
+        },
+        "type": "array"
+      },
+      "description": "Named tool sequences for common agent tasks.",
+      "type": "object"
+    }
+  },
+  "required": [
+    "server",
+    "stats",
+    "network_synonyms",
+    "workflows",
+    "common_pitfalls",
+    "documentation",
+    "agent_skills"
+  ],
+  "type": "object"
+}

First observedJul 28, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description adds beyond these by stating the tool is 'keyless', returns static onboarding docs rather than live data, and is intended to be read once at session start. This gives useful behavioral context without contradicting annotations.

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 dense but every sentence earns its place: purpose and contents are front-loaded, usage triggers are explicit, alternatives are named, and the parameter note closes it out. No filler or repetition of schema details.

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 single-parameter read-only tool with a rich annotation set and an output schema, the description covers everything an agent needs: what the tool returns, when to call it, how to distinguish it from siblings, and the only parameter requirement. Nothing important 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?

Schema coverage is 100%, so the schema already fully documents the `rationale` parameter including length constraints and privacy guidance. The description only adds 'Takes no parameters beyond a short rationale,' which is marginal but not necessary given the schema's completeness.

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 identifies a specific verb and resource: 'Get the static agent onboarding guide for this server' and enumerates its contents (workflows, network name synonyms, call sequences, pitfalls). It also explicitly distinguishes itself from siblings by noting this is not live market data and pointing to getNetworks and getStats for those needs.

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?

The description gives explicit when-to-use guidance: 'Read it once at the start of a session before your first query, or when asked...' and lists concrete natural-language triggers. It also names alternatives (getNetworks, getStats) and explains what this tool should not be used for.

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?