Dexscreener

Token Boosts Top

token_boosts_top

Read-onlyIdempotent

Most-boosted tokens, optionally filtered to a chain / token.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`chain`	No
`token`	No	Token address (chain required if passed)

Output Schema

TableJSON Schema

Name	Required	Description
`chain`	No	Chain filter that was applied, when one was passed
`token`	No	Token filter that was applied, when one was passed
`boosts`	Yes	Boost entries
`filtered`	Yes	Whether a chain/token filter was applied
`boost_count`	Yes	Number of boost entries returned

Schema Changelog

Changes observed during successful MCP inspections.

Changed12 schema fields changedSep 9, 2026

changedInput schema / examples

Previous value: -[
-  {
-    "chain": "ethereum"
-  },
-  {
-    "chain": "solana",
-    "token": "EPjFWaLb3hyccqaLmc4ZeAQJ5v4J8DTfWWrpqkc2Egw"
-  }
-]New value: +[
+  {},
+  {
+    "chain": "solana"
+  }
+]

changedOutput schema / description

Previous value: -"Most-boosted tokens optionally filtered by chain/token"New value: +"Most-boosted tokens, optionally filtered to a chain/token"

addedOutput schema / properties / boost_count

Added value: +{
+  "description": "Number of boost entries returned",
+  "type": "number"
+}

changedOutput schema / properties / boosts / description

Previous value: -"Top boosted tokens"New value: +"Boost entries"

changedOutput schema / properties / boosts / items / properties / amount / description
```
Previous value: -"Total boost amount"New value: +"Boost amount"
```

addedOutput schema / properties / boosts / items / properties / description

Added value: +{
+  "description": "Token description",
+  "type": [
+    "string",
+    "null"
+  ]
+}

addedOutput schema / properties / boosts / items / properties / totalAmount

Added value: +{
+  "description": "Cumulative boost amount",
+  "type": [
+    "number",
+    "null"
+  ]
+}

addedOutput schema / properties / chain

Added value: +{
+  "description": "Chain filter that was applied, when one was passed",
+  "type": "string"
+}

addedOutput schema / properties / filtered

Added value: +{
+  "description": "Whether a chain/token filter was applied",
+  "type": "boolean"
+}

removedOutput schema / properties / schemaVersion

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

addedOutput schema / properties / token

Added value: +{
+  "description": "Token filter that was applied, when one was passed",
+  "type": "string"
+}

addedOutput schema / required

Added value: +[
+  "boost_count",
+  "filtered",
+  "boosts"
+]

First observedJun 26, 2026

TDQS

A3.6/5.0

Behavior3/5

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

Annotations already establish readOnly, idempotent, non-destructive behaviorging; the description adds 'Most-boosted' (implying ranking/sort) and optional filtering. It does not disclose ordering, limit/default count, or what 'boosted' means, but for a simple read it is adequate.

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?

Single sentence, front-loaded with the resource ('most-boosted tokens') and optional filtering. Every word adds signal; no filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Low complexity (2 optional params, readOnly/idempotent/ non-destructive annotations, output schema exists), so a terse description suffices. It lacks only minor guidance such as that chain is required when token is supplied, though the schema already states that.

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 description mentions 'chain / token' filter semantics, but only token is described in the schema; chain is just a string param name with no format or domain guidance. The schema covers 50% (token has a description), and the description partially compensates by signaling both params are filters, yet no detail on chain values or token format.

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 states the resource ('most-boosted tokens') and the optional filtering behavior ('filtered to a chain / token'), so an agent can tell it is a read-style list operation. It lacks an explicit verb like 'list' or 'get', and no sibling has a directly similar name, so it doesn't fully differentiate but is still clear.

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 the tool is for querying top boosted tokens with optional chain/token filters strand, but it gives no explicit when-to-use guidance or alternatives. Sibling names like latest_boosted_tokens and compare_entities suggest nearby tools, but the description does not say when this one should be chosen over them.

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.