Skip to main content
Glama
pump.fun MCP Server

pump.fun MCP Server

by blixtrade

whale_trades

Track large buys and sells on a Solana token over the last 24 hours, with net flow and ranked net buyers and sellers.

Instructions

Large buys and sells on a Solana token over the last 24 hours, with net flow and the biggest net buyers and sellers.

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": "whale_trades"
  }
}

Input Schema

NameRequiredDescriptionDefault
mintYesSolana token mint address (base58).
limitNo
minUsdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3/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 behavioral burden. It usefully discloses the fixed 24-hour window and summarizes the returned content, but says nothing about what 'large' means relative to minUsd, whether the window is configurable, result ordering, or rate/data-source caveats.

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?

A single front-loaded sentence that leads with the core resource and appends scope and payload without filler. It is efficient, though the trailing clause list is slightly crammed rather than structured.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 3-parameter read tool with no output schema and no annotations, the description covers intent and rough output shape. It leaves out how limit/minUsd shape results and what the net-flow figures represent, which an agent would need to call it confidently.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Only mint has a schema description (33% coverage), so limit and minUsd are undocumented in both places. The description gestures at 'large' filtering and a 24h window but never explains that minUsd sets the trade-size threshold or that limit caps rows, leaving two of three parameters without meaning.

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?

Names a concrete resource (large buys and sells on a Solana token) with a clear scope (last 24 hours) and previews the payload (net flow, biggest net buyers and sellers). It does not explicitly differentiate itself from siblings such as wallet_trades or top_holders, so it stops short of a 5.

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 when-to-use guidance, no exclusions, and no named alternative. The only usable signal is the implied fit for whale/large-order analysis, which the agent must infer from the phrase 'large buys and sells'; nothing tells it when to prefer wallet_trades or top_holders instead.

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