Skip to main content
Glama
jun85664396

Pump Fun Data MCP Server

by jun85664396

get_coins

Retrieve a paginated list of cryptocurrency tokens from Pump.fun with customizable sorting, filtering, and display options.

Instructions

Get a list of coins

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
offsetNoThe offset to start from (default: 0)
limitNoThe number of coins to return (default: 24)
sortNoThe field to sort by (market_cap, last_trade_timestamp, created_timestamp, last_reply)market_cap
includeNsfwNoInclude NSFW coins (default: true)
orderNoThe order to sort by (ASC, DESC)DESC

Implementation Reference

  • index.ts:93-101 (handler)
    The switch case within handleToolCall that executes the logic for the 'get_coins' tool by setting the API URL to '/coins' and calling fetchPumpFunData with arguments.
    case "get_coins":
        url = PUMP_FUN_API_URL+'/coins';
        return {
          content: [{
            type: "text",
            text: JSON.stringify((await fetchPumpFunData(url, args)))
          }],
          isError: false,
        };
  • The tool definition in the TOOLS array, including name, description, and inputSchema for 'get_coins'.
    {
        name: "get_coins",
        description: "Get a list of coins",
        inputSchema: {
            type: "object",
            properties: {
                offset: { type: "number", description: "The offset to start from (default: 0)", default: 0 },
                limit: { type: "number", description: "The number of coins to return (default: 24)", default: 24 },
                sort: { type: "string", description: "The field to sort by (market_cap, last_trade_timestamp, created_timestamp, last_reply)", default: "market_cap" },
                includeNsfw: { type: "boolean", description: "Include NSFW coins (default: true)", default: true },
                order: { type: "string", description: "The order to sort by (ASC, DESC)", default: "DESC"},
    
            },
            required: [],
        },
    },
  • index.ts:148-150 (registration)
    Registers the ListToolsRequestHandler which exposes the 'get_coins' tool via the TOOLS array.
    server.setRequestHandler(ListToolsRequestSchema, async () => ({
        tools: TOOLS,
      }));
  • index.ts:152-154 (registration)
    Registers the CallToolRequestHandler which dispatches tool calls to handleToolCall based on the tool name.
    server.setRequestHandler(CallToolRequestSchema, async (request) =>
      handleToolCall(request.params.name, request.params.arguments ?? {})
    );
  • Helper function used by the tool handlers to make authenticated HTTP requests to the pump.fun API.
    async function fetchPumpFunData(url: string, params: any) {
        const headers = {
            'accept': '*/*',
            'accept-language': 'en-US,en;q=0.9',
            'content-type': 'application/json',
            'origin': 'https://pump.fun',
            'priority': 'u=1, i',
            'referer': 'https://pump.fun/',
            'sec-ch-ua': '"Chromium";v="134", "Not:A-Brand";v="24", "Google Chrome";v="134"',
            'sec-ch-ua-mobile': '?0',
            'sec-ch-ua-platform': '"macOS"',
            'user-agent': 'Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/134.0.0.0 Safari/537.36'
        };
        const response = await axios.get(url, { params, headers });
        if (response.status !== 200 || !response.data) {
            throw new Error(`Failed to fetch data: ${response.status}`);
        }
        return response.data;
    }
Behavior2/5

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

With no annotations provided, the description carries full burden but only states basic functionality. It doesn't disclose behavioral traits such as whether this is a read-only operation, potential rate limits, authentication needs, pagination behavior, or what happens with invalid parameters. For a list tool with 5 parameters, this leaves significant gaps.

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 wasted words. It's appropriately sized for a simple list tool and front-loads the core purpose immediately.

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 no annotations, no output schema, and 5 parameters, the description is incomplete. It doesn't explain return values, error conditions, or behavioral context needed for proper tool invocation. For a tool with this complexity, the description should do more to guide the agent.

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?

Schema description coverage is 100%, so all parameters are documented in the schema. The description adds no additional meaning about parameters beyond implying a list operation. This meets the baseline of 3 since the schema does the heavy lifting, but the description doesn't compensate or enhance understanding.

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 a list of coins' clearly states the action (get) and resource (coins), but it's vague about scope and doesn't distinguish from siblings like get_coin_info (single coin) or get_featured_coins (filtered subset). It lacks specificity about what kind of list this returns.

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?

No guidance is provided on when to use this tool versus alternatives like get_coin_info or get_featured_coins. The description doesn't mention any context, prerequisites, or exclusions, leaving the agent to infer usage from parameter names alone.

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/jun85664396/pump-fun-data-mcp'

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