DexPaprika

getTokenDetails

Read-onlyIdempotent

Get one token's data and metadata by contract address on one network: multi-timeframe price and volume metrics, plus name, website, Twitter, and Telegram links, returned as a single token object. Read-only and keyless. Use for 'price and volume for 0x... on Base' or 'tell me about this token'. If you only have a symbol like WETH, call search first to resolve the address and network. For many tokens' prices at once use getTokenMultiPrices; for the pools holding this token use getTokenPools. Params: network (required slug); token_address (required contract address, e.g. 'JUPyiwrYJFskUPiHa7hkeR8VUtAeFoSYbKedZNsDvCN' on solana).

Input Schema

TableJSON Schema

Name	Required	Description
`network`	Yes	REQUIRED: Network ID from getNetworks (e.g., 'ethereum', 'solana')
`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.
`token_address`	Yes	REQUIRED: Token contract address (e.g., 'JUPyiwrYJFskUPiHa7hkeR8VUtAeFoSYbKedZNsDvCN' for Jupiter on Solana)

Output Schema

TableJSON Schema

Name	Required	Description
`id`	No
`name`	No
`chain`	No
`symbol`	No
`summary`	No
`website`	No
`added_at`	No
`decimals`	No
`has_image`	No
`description`	No
`price_stats`	No
`total_supply`	No	Raw on-chain total supply. Big numbers may overflow JS Number; handle as string for tokens with 18+ decimals.

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": {
+    "added_at": {
+      "type": "string"
+    },
+    "chain": {
+      "type": "string"
+    },
+    "decimals": {
+      "type": "number"
+    },
+    "description": {
+      "type": "string"
+    },
+    "has_image": {
+      "type": "boolean"
+    },
+    "id": {
+      "type": "string"
+    },
+    "name": {
+      "type": "string"
+    },
+    "price_stats": {},
+    "summary": {},
+    "symbol": {
+      "type": "string"
+    },
+    "total_supply": {
+      "description": "Raw on-chain total supply. Big numbers may overflow JS Number; handle as string for tokens with 18+ decimals.",
+      "type": [
+        "number",
+        "string"
+      ]
+    },
+    "website": {
+      "type": "string"
+    }
+  },
+  "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 flags by stating the call is keyless, returns a single token object, and includes multi-timeframe metrics plus metadata. This gives the agent practical behavioral context such as no authentication and expected return shape 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?

Every sentence serves a distinct purpose: state the operation, confirm read-only/keyless, provide example queries, route to alternatives, and summarize parameters. It is front-loaded with the core purpose and contains no filler, tautology, or redundant exposition.

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?

Given a full output schema, high schema coverage, and rich annotations, the description provides everything needed to select and invoke the tool correctly. It handles the ambiguous symbol-only case, names related sibling tools, and confirms behavioral expectations. No critical information 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 input schema covers all three required parameters with descriptions, so the baseline is 3. The description adds marginal extra meaning like 'slug' for network and an example token address, but mostly restates what is already in the schema. It does not significantly deepen parameter understanding.

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 opens with a specific verb and resource: 'Get one token's data and metadata by contract address on one network.' It lists concrete contents (price/volume metrics, name, website, Twitter, Telegram links) and explicitly distinguishes itself from siblings like getTokenMultiPrices and getTokenPools. An agent can clearly tell what this tool does and does not do.

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 example user intents ('price and volume for 0x... on Base', 'tell me about this token'), instructs to call search first when only a symbol is known, and names alternatives for bulk prices (getTokenMultiPrices) and pools (getTokenPools). This is comprehensive when/when-not guidance with no ambiguity.

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?