Skip to main content
Glama
jun85664396

Pump Fun Data MCP Server

by jun85664396

get_coin_info

Retrieve detailed coin information by providing its mint ID, enabling users to access essential data for analysis and decision-making.

Instructions

Get information about a coin

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
mintIdYesThe mint id of the coin(coin address)

Implementation Reference

  • The switch case within handleToolCall that executes the get_coin_info tool. It constructs the API URL using the mintId from arguments and fetches the coin information from the pump.fun API, returning the JSON data.
    case "get_coin_info":
        url = PUMP_FUN_API_URL+'/coins/'+args.mintId;
        return {
          content: [{
            type: "text",
            text: JSON.stringify((await fetchPumpFunData(url, {})))
          }],
          isError: false,
        };
  • The input schema definition for the get_coin_info tool, specifying the required 'mintId' parameter.
    inputSchema: {
        type: "object",
        properties: {
            mintId: { type: "string", description: "The mint id of the coin(coin address)" },
        },
        required: ["mintId"],
    },
  • index.ts:43-53 (registration)
    The tool registration in the TOOLS array, defining name, description, and input schema for get_coin_info.
    {
        name: "get_coin_info",
        description: "Get information about a coin",
        inputSchema: {
            type: "object",
            properties: {
                mintId: { type: "string", description: "The mint id of the coin(coin address)" },
            },
            required: ["mintId"],
        },
    }
  • index.ts:148-150 (registration)
    Registers the ListToolsRequestHandler which returns the TOOLS list including get_coin_info.
    server.setRequestHandler(ListToolsRequestSchema, async () => ({
        tools: TOOLS,
      }));
  • index.ts:152-154 (registration)
    Registers the CallToolRequestHandler which dispatches to handleToolCall based on tool name.
    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 of behavioral disclosure. It only states the action ('Get information') without detailing traits like whether it's read-only, requires authentication, has rate limits, or what happens on errors. This is inadequate 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.

Conciseness4/5

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

The description is a single, efficient sentence ('Get information about a coin') that is front-loaded and wastes no words. However, it's overly concise to the point of under-specification, lacking necessary details for full clarity.

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 simplicity (1 parameter, no output schema, no annotations), the description is incomplete. It doesn't explain what 'information' is returned (e.g., price, metadata), potential errors, or how it differs from siblings, leaving gaps for the agent to navigate.

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?

The input schema has 100% description coverage, with the parameter 'mintId' documented as 'The mint id of the coin (coin address)'. The description adds no additional meaning beyond this, such as format examples or constraints, so it meets the baseline for high schema coverage.

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 states the tool's purpose ('Get information about a coin') with a clear verb ('Get') and resource ('coin'), but it's vague about what specific information is retrieved. It doesn't distinguish from sibling tools like 'get_coins' (likely lists multiple coins) or 'get_featured_coins' (likely highlights specific coins), missing differentiation.

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 provides no guidance on when to use this tool versus alternatives. It doesn't mention sibling tools like 'get_coins' or 'get_featured_coins', nor does it specify prerequisites or exclusions, leaving the agent to infer usage from context 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