Skip to main content
Glama
openSVM

DexScreener MCP Server

by openSVM

get_top_boosted_tokens

Retrieve tokens with the highest active boosts from DexScreener to identify trending assets across multiple blockchains.

Instructions

Get tokens with most active boosts

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The core handler function that fetches the top boosted tokens from the DexScreener API endpoint '/token-boosts/top/v1' using the service's internal fetch method with rate limiting.
    async getTopBoostedTokens(): Promise<TokenBoost[]> {
      return this.fetch<TokenBoost[]>('/token-boosts/top/v1', tokenRateLimiter);
    }
  • Input schema definition for the tool in the MCP server capabilities declaration, specifying no input parameters required.
    get_top_boosted_tokens: {
      description: 'Get tokens with most active boosts',
      inputSchema: {
        type: 'object',
        properties: {},
        required: [],
      },
    },
  • src/index.ts:315-317 (registration)
    Registration and dispatch logic in the MCP callTool request handler switch statement, invoking the DexScreenerService method.
    case 'get_top_boosted_tokens':
      result = await this.dexService.getTopBoostedTokens();
      break;
  • Tool schema returned in the MCP listTools request handler response.
      name: 'get_top_boosted_tokens',
      description: 'Get tokens with most active boosts',
      inputSchema: {
        type: 'object',
        properties: {},
        required: [],
      },
    },
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the tool 'gets' tokens, implying a read operation, but doesn't specify any behavioral traits such as rate limits, authentication needs, data freshness, or what constitutes 'most active boosts.' This leaves significant gaps in understanding how the tool behaves.

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, efficient sentence: 'Get tokens with most active boosts.' It is front-loaded and wastes no words, making it highly concise and well-structured for its purpose.

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

Completeness2/5

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

Given the lack of annotations and output schema, the description is incomplete. It doesn't explain what 'most active boosts' means, how results are sorted or limited, or what the return format looks like. For a tool that likely returns a list of tokens, more context is needed to understand its output and usage fully.

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?

The tool has 0 parameters, and schema description coverage is 100%, so no parameter documentation is needed. The description doesn't add parameter semantics, but this is acceptable given the lack of parameters, aligning with the baseline expectation for zero-parameter tools.

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 the tool's purpose: 'Get tokens with most active boosts.' It uses a specific verb ('Get') and identifies the resource ('tokens with most active boosts'). However, it doesn't explicitly differentiate from sibling tools like 'get_latest_boosted_tokens' or 'get_latest_token_profiles,' which appear related but have different scopes.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention any context, prerequisites, or exclusions, nor does it reference sibling tools like 'get_latest_boosted_tokens' or 'get_token_orders' that might be used in similar scenarios.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/openSVM/dexscreener-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server