Dexscreener

Get Token

get_token

Read-onlyIdempotent

All trading pairs for a token address on one chain.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`chain`	Yes	Chain id
`token_address`	Yes	Token contract address

Output Schema

TableJSON Schema

Name	Required	Description
`chain`	Yes	Chain id that was queried
`pairs`	Yes	Pools trading this token on that chain
`pair_count`	Yes	Number of pools returned (>=1; an empty result raises not_found)
`token_address`	Yes	Token contract address that was queried

Schema Changelog

Changes observed during successful MCP inspections.

Changed18 schema fields changedSep 9, 2026

changedOutput schema / description

Previous value: -"Token with all trading pairs response"New value: +"Every DEX Screener pool for one token address on one chain"

addedOutput schema / properties / chain

Added value: +{
+  "description": "Chain id that was queried",
+  "type": "string"
+}

addedOutput schema / properties / pair_count

Added value: +{
+  "description": "Number of pools returned (>=1; an empty result raises not_found)",
+  "type": "number"
+}

changedOutput schema / properties / pairs / description

Previous value: -"Array of trading pairs for the token"New value: +"Pools trading this token on that chain"

addedOutput schema / properties / pairs / items / properties / baseToken / description
```
Added value: +"Base token address/name/symbol"
```
addedOutput schema / properties / pairs / items / properties / fdv / description
```
Added value: +"Fully diluted valuation"
```
addedOutput schema / properties / pairs / items / properties / liquidity / description
```
Added value: +"Liquidity in USD and both tokens"
```

addedOutput schema / properties / pairs / items / properties / marketCap

Added value: +{
+  "description": "Market capitalisation",
+  "type": [
+    "number",
+    "null"
+  ]
+}

addedOutput schema / properties / pairs / items / properties / priceNative / description
```
Added value: +"Price in the quote token"
```
addedOutput schema / properties / pairs / items / properties / priceUsd / description
```
Added value: +"Price in USD"
```
changedOutput schema / properties / pairs / items / properties / priceUsd / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```
addedOutput schema / properties / pairs / items / properties / quoteToken / description
```
Added value: +"Quote token address/name/symbol"
```
addedOutput schema / properties / pairs / items / properties / txns / description
```
Added value: +"Buy/sell counts over m5/h1/h6/h24"
```
addedOutput schema / properties / pairs / items / properties / volume / description
```
Added value: +"Volume over m5/h1/h6/h24"
```

changedOutput schema / properties / pairs / type

Previous value: -[
-  "array",
-  "null"
-]New value: +"array"

removedOutput schema / properties / schemaVersion

Removed value: -{
-  "description": "API schema version",
-  "type": "string"
-}

addedOutput schema / properties / token_address

Added value: +{
+  "description": "Token contract address that was queried",
+  "type": "string"
+}

addedOutput schema / required

Added value: +[
+  "chain",
+  "token_address",
+  "pair_count",
+  "pairs"
+]

First observedJun 26, 2026

TDQS

A3.7/5.0

Behavior3/5

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

Annotations already declare this as a safe, read-only, idempotent operation, so the description does not need to repeat those guarantees. It adds the useful behavioral context that the result is trading pairs rather than token metadata, but it does not disclose additional traits such as ordering, pagination, or response shape beyond what the output schema likely covers.

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 a single, compact sentence with no filler words. It front-loads the essential scope—'all trading pairs'—and immediately qualifies it with the token and chain constraints, making it easy for an agent to parse quickly.

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 simple query tool with an output schema, annotations, and fully documented parameters, the description is sufficient. It tells the agent exactly what domain the tool covers, and the remaining execution details are available in the schema and annotations.

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 description coverage is 100%, with both 'chain' and 'token_address' clearly documented in the input schema. The description does not add extra parameter meaning beyond restating that the lookup is scoped to one token address on one chain, so it meets the baseline without exceeding it.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states that the tool returns all trading pairs for a token address on a specific chain, which makes the core function understandable. It lacks an explicit verb like 'Returns' and does not directly name sibling tools, but the phrase 'All trading pairs' distinguishes it from pair-specific or search-oriented siblings.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies when to use the tool: when you need the complete set of trading pairs for one token on one chain. However, it gives no explicit guidance on when not to use it or how it compares to alternatives like get_pair or search_pairs, leaving usage decisions to inference.

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

All Dexscreener 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.