Skip to main content
Glama
coinpaprika

DexPaprika (CoinPaprika)

Official
by coinpaprika
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

getTokenDetails

Read-onlyIdempotent

Fetch detailed token data by contract address on any network: price, volume, and metadata like website and social links. Resolves symbols via search when needed.

Instructions

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
NameRequiredDescriptionDefault
networkYesREQUIRED: Network ID from getNetworks (e.g., 'ethereum', 'solana')
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.
token_addressYesREQUIRED: Token contract address (e.g., 'JUPyiwrYJFskUPiHa7hkeR8VUtAeFoSYbKedZNsDvCN' for Jupiter on Solana)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNo
nameNo
chainNo
symbolNo
summaryNo
websiteNo
added_atNo
decimalsNo
has_imageNo
descriptionNo
price_statsNo
total_supplyNoRaw on-chain total supply. Big numbers may overflow JS Number, so handle as string for tokens with 18+ decimals.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.5.0
    • changedOutput schema / properties / total_supply / description
      Previous value: -"Raw on-chain total supply. Big numbers may overflow JS Number — handle as string for tokens with 18+ decimals."New value: +"Raw on-chain total supply. Big numbers may overflow JS Number, so handle as string for tokens with 18+ decimals."
  2. Changed6 schema fields changedv1.0.1
    • changedInput schema / properties / network / description
      Previous value: -"Network ID from getNetworks (e.g., \"ethereum\", \"solana\")"New value: +"REQUIRED: Network ID from getNetworks (e.g., 'ethereum', 'solana')"
    • addedInput schema / properties / rationale
      Added value: +{
+  "description": "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.",
+  "maxLength": 500,
+  "minLength": 20,
+  "type": "string"
+}
    • removedInput schema / properties / tokenAddress
      Removed value: -{
-  "description": "Token address or identifier",
-  "type": "string"
-}
    • addedInput schema / properties / token_address
      Added value: +{
+  "description": "REQUIRED: Token contract address (e.g., 'JUPyiwrYJFskUPiHa7hkeR8VUtAeFoSYbKedZNsDvCN' for Jupiter on Solana)",
+  "type": "string"
+}
    • changedInput schema / required
      Previous value: -[
-  "network",
-  "tokenAddress"
-]New value: +[
+  "network",
+  "token_address",
+  "rationale"
+]
    • 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"
+}
  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 readOnlyHint=true, idempotentHint=true, openWorldHint=true, destructiveHint=false. The description adds 'Read-only and keyless' which reinforces the safety profile and adds the keyless auth detail beyond annotations. Doesn't disclose rate limits but annotations carry the load appropriately.

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 earns its place: main description, usage example, symbol-resolution edge case, and sibling pointer. The final sentence is an info-dense list of both alternatives in a compact form. No fluff, no repetition of schema content.

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 there's an output schema (return value documented elsewhere), 100% param coverage, and rich annotations, the description is complete. It covers edge cases (symbol-only queries), access model (keyless), and disambiguation from 17 siblings. Nothing important is left unexplained.

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 baseline is 3. The description adds value by explaining the network param is a 'slug', providing a real example for token_address, and adding entity resolution workflow guidance ('call search first') that anticipates a common failure mode not in 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?

Specific verb ('Get') + resource ('one token's data and metadata by contract address') + scope ('on one network'). Clearly distinguishes from siblings by explicitly naming getTokenMultiPrices and getTokenPools as alternatives for different 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?

Explicit when-to-use ('price and volume for 0x... on Base'), what to do with only a symbol ('call search first to resolve the address'), and explicit alternatives ('use getTokenMultiPrices', 'use getTokenPools'). This is exemplary usage guidance.

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

Deploy Server

Other Tools