Skip to main content
Glama
openSVM

DexScreener MCP Server

by openSVM

get_latest_token_profiles

Retrieve current token profiles from DexScreener to analyze cryptocurrency assets and their market data across multiple blockchains.

Instructions

Get the latest token profiles

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The primary handler function that implements the core logic of the 'get_latest_token_profiles' tool by making a rate-limited API call to DexScreener's latest token profiles endpoint.
    async getLatestTokenProfiles(): Promise<TokenProfile[]> {
      return this.fetch<TokenProfile[]>('/token-profiles/latest/v1', tokenRateLimiter);
    }
  • src/index.ts:97-104 (registration)
    Tool registration in MCP server capabilities, defining the tool name, description, and empty input schema.
    get_latest_token_profiles: {
      description: 'Get the latest token profiles',
      inputSchema: {
        type: 'object',
        properties: {},
        required: [],
      },
    },
  • Dispatch logic in the MCP 'tools/call' request handler that invokes the DexScreenerService handler for this tool.
    case 'get_latest_token_profiles':
      result = await this.dexService.getLatestTokenProfiles();
      break;
  • Tool schema definition returned by the MCP 'tools/list' handler, matching the registration schema.
    name: 'get_latest_token_profiles',
    description: 'Get the latest token profiles',
    inputSchema: {
      type: 'object',
      properties: {},
      required: [],
    },
Behavior1/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 but only states the action without any behavioral traits. It does not cover aspects like read-only vs. destructive operations, authentication needs, rate limits, or response format, making it inadequate 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.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is concise with a single sentence, but it is under-specified rather than efficiently structured. It lacks front-loaded critical information and does not earn its place by adding value, resulting in a mediocre score for conciseness.

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 does not explain what 'latest' means, what data 'token profiles' include, or how results are returned, failing to provide sufficient context for the agent to understand the tool's behavior and output.

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 with 100% schema description coverage, so no parameter information is needed. The description does not add semantics beyond the schema, but this is acceptable as the baseline for zero parameters is 4, since there are no parameters to document.

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

Purpose2/5

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

The description 'Get the latest token profiles' restates the tool name 'get_latest_token_profiles' almost verbatim, making it tautological. It provides a vague purpose without specifying what 'latest' means (e.g., by time, update frequency) or what 'token profiles' entail, failing to distinguish it from sibling tools like 'get_top_boosted_tokens' or 'get_latest_boosted_tokens'.

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

Usage Guidelines1/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 does not mention context, prerequisites, or exclusions, and fails to differentiate it from sibling tools such as 'get_latest_boosted_tokens' or 'search_pairs', leaving 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