Skip to main content
Glama
pump.fun MCP Server

pump.fun MCP Server

by blixtrade

token_info

Retrieves price, market cap, liquidity, volume, price change, and age for a Solana token from its deepest DEX pool using the token mint address.

Instructions

Price, market cap, liquidity, volume, price change and age for a Solana token, from its deepest DEX pool.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "mint": "<mint>"
    },
    "name": "token_info"
  }
}

Input Schema

NameRequiredDescriptionDefault
mintYesSolana token mint address (base58).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It does disclose a meaningful behavioral trait beyond the name: values come from the token's deepest DEX pool rather than an aggregate across pools, which affects how the numbers should be interpreted. However, it says nothing about behavior for tokens with no pool or an invalid mint, nor about rate limits or freshness of the data.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

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

One compact sentence with the returned fields front-loaded and no filler. It omits an explicit verb-phrase subject ("Returns...") but remains immediately parseable, with zero redundant wording.

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?

For a one-parameter lookup with no output schema, the enumeration of returned metrics is exactly the information an agent needs and is present. The remaining gaps—edge cases for unresolved mints or missing pools, and data staleness—are minor for a tool this simple, though the absence of annotations means they would have been worth one more clause.

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?

There is a single required parameter with 100% schema description coverage already stating it is a Solana token mint address in base58. The description adds no format, validation, or derivation detail beyond that, so the schema does all the work and the baseline of 3 applies.

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 names a specific resource (a Solana token) and enumerates the exact metrics returned: price, market cap, liquidity, volume, price change, and age. It also scopes the data source ("deepest DEX pool"), which distinguishes it from an aggregate or screening tool. It stops short of naming a sibling like rug_check, so differentiation is inferred rather than stated.

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?

Usage is only implied: an agent can infer this is the tool for fetching market metrics once it has a mint address. There is no explicit when-to-use, no guidance on when to prefer rug_check or screen_tokens instead, and no prerequisites or caveats. Adequate for a narrow single-purpose lookup, but the agent must reason about selection on its own.

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