Skip to main content
Glama
openSVM

DexScreener MCP Server

by openSVM

get_latest_boosted_tokens

Retrieve recently promoted cryptocurrency tokens from decentralized exchanges to identify emerging market opportunities.

Instructions

Get the latest boosted tokens

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The core handler function that executes the tool logic by fetching the latest boosted tokens from the DexScreener API endpoint '/token-boosts/latest/v1' using the service's internal fetch method with rate limiting.
    async getLatestBoostedTokens(): Promise<TokenBoost[]> {
      return this.fetch<TokenBoost[]>('/token-boosts/latest/v1', tokenRateLimiter);
    }
  • src/index.ts:105-112 (registration)
    Registers the tool in the MCP server capabilities, defining its description and input schema (empty object, no required params).
    get_latest_boosted_tokens: {
      description: 'Get the latest boosted tokens',
      inputSchema: {
        type: 'object',
        properties: {},
        required: [],
      },
    },
  • Dispatches the tool call in the MCP 'tools/call' request handler by invoking the DexScreenerService method.
    case 'get_latest_boosted_tokens':
      result = await this.dexService.getLatestBoostedTokens();
      break;
  • Defines the tool schema returned by the MCP 'tools/list' request handler.
    name: 'get_latest_boosted_tokens',
    description: 'Get the latest boosted tokens',
    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 only states what the tool does ('Get the latest boosted tokens') without explaining behavioral traits like whether it's read-only, requires authentication, has rate limits, or what 'latest' means (e.g., time-based, count-based). This is a significant gap for a tool with zero annotation coverage.

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 with zero waste. It's appropriately sized for a simple tool and front-loaded with the core action. Every word earns its place, making it highly concise and well-structured.

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 tool's complexity (simple retrieval) but lack of annotations and output schema, the description is incomplete. It doesn't explain what 'boosted tokens' are, how 'latest' is defined, or what the return format looks like. For a tool with no structured data to rely on, this leaves critical gaps in understanding.

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 the schema description coverage is 100%, so there are no parameters to document. The description doesn't need to add parameter semantics, and it doesn't introduce any confusion. A baseline score of 4 is appropriate as the description doesn't compensate for missing param info, but none is needed.

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

Purpose3/5

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

The description 'Get the latest boosted tokens' states a clear verb ('Get') and resource ('boosted tokens'), but it's vague about what 'boosted tokens' means and doesn't distinguish it from sibling tools like 'get_top_boosted_tokens' or 'get_latest_token_profiles'. It provides a basic purpose but lacks specificity.

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 offers no guidance on when to use this tool versus alternatives. It doesn't mention any context, prerequisites, or exclusions, such as how it differs from 'get_top_boosted tokens' or other siblings. This leaves the agent with no usage direction.

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