Skip to main content
Glama
jun85664396

Pump Fun Data MCP Server

by jun85664396

get_featured_coins

Retrieve a curated list of featured cryptocurrencies from the Pump.fun platform, allowing users to filter results by offset, limit, and NSFW content preferences.

Instructions

Get a list of featured coins

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
offsetNoThe offset to start from (default: 0)
limitNoThe number of coins to return (default: 24)
includeNsfwNoInclude NSFW coins (default: true)

Implementation Reference

  • index.ts:84-92 (handler)
    Handler logic for the 'get_featured_coins' tool: sets the API URL to fetch featured coins from pump.fun and returns the JSON data.
    case "get_featured_coins":
       url = PUMP_FUN_API_URL+'/coins/for-you';
       return {
          content: [{
            type: "text",
            text: JSON.stringify((await fetchPumpFunData(url, args)))
          }],
          isError: false,
      };
  • Input schema for the 'get_featured_coins' tool, defining optional parameters: offset, limit, includeNsfw.
    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 },
            includeNsfw: { type: "boolean", description: "Include NSFW coins (default: true)", default: true },
        }
    },
  • index.ts:15-26 (registration)
    Registration of the 'get_featured_coins' tool in the TOOLS array, including name, description, and schema.
    {
        name: "get_featured_coins",
        description: "Get a list of featured 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 },
                includeNsfw: { type: "boolean", description: "Include NSFW coins (default: true)", default: true },
            }
        },
    },
  • Helper function to make authenticated API requests to pump.fun endpoints, used by the get_featured_coins handler.
    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;
    }
  • index.ts:152-154 (registration)
    Registers the CallToolRequestSchema handler which dispatches to handleToolCall based on tool name, enabling execution of get_featured_coins.
    server.setRequestHandler(CallToolRequestSchema, async (request) =>
      handleToolCall(request.params.name, request.params.arguments ?? {})
    );
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It states the action but doesn't disclose behavioral traits such as whether this is a read-only operation, potential rate limits, authentication needs, or what the return format looks like. This is a significant gap for a tool with no 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 front-loaded and appropriately sized for its purpose, making it easy to parse quickly.

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 complexity of a list-fetching tool with no annotations and no output schema, the description is incomplete. It doesn't explain what 'featured' entails, the response structure, or any behavioral context, leaving the agent with insufficient information to use the tool effectively beyond basic parameters.

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 the schema fully documents the parameters (offset, limit, includeNsfw). The description adds no additional meaning beyond what the schema provides, such as explaining why 'featured' coins might be filtered or how parameters interact. Baseline 3 is appropriate when the schema does the heavy lifting.

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 featured coins' clearly states the verb ('Get') and resource ('featured coins'), but it's vague about what 'featured' means and doesn't distinguish from sibling tools like 'get_coins' or 'get_coin_info'. 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?

No guidance is provided on when to use this tool versus alternatives like 'get_coins' or 'get_coin_info'. The description implies usage for featured coins but doesn't specify context, exclusions, or prerequisites, leaving the agent without clear 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/jun85664396/pump-fun-data-mcp'

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