Skip to main content
Glama
Sign In

pumpdata

by fun.pumpdata
OverviewDiscussionsAdmin

top_wallets

Read-onlyIdempotent

Free. The pump.fun wallet leaderboard, ranked by each wallet's own profit. (Oct 31: the follower ranking, sort copyable, is withdrawn until it is rebuilt at PumpSwap's real fees; at them, copying the best-scored wallets 1 slot behind lost money in all seven weeks tested.) The wallets win over their whole record (took out 10+ SOL and 1% more than they put in over 20+ coin-weeks) and traded in the last ~20 days, each with why, its SOL in and out, its coins and its recent pace (trades a day, median hold). followable: true keeps the ones a copier can keep up with (under 20 trades a day, a median hold of 2 minutes or more, under half its trades fast). For: who should I copy trade, the best pump.fun traders, smart money wallets. Not pump.fun's own leaderboard, which ranks recent profit. Then wallet_records for any wallet's full record.

Input Schema

NameRequiredDescriptionDefault
sortNoown (default): by the wallet's own profit; copyable: by what a follower 1 slot behind made, once a build charges PumpSwap's real fees (until then, own)
limitNowallets to return, best first; default 25
followableNoonly wallets a copier can keep up with; default false

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / sort / description
      Previous value: -"copyable (default): by what a follower 1 slot behind made; own: by the wallet's own profit"New value: +"own (default): by the wallet's own profit; copyable: by what a follower 1 slot behind made, once a build charges PumpSwap's real fees (until then, own)"
  2. Changed1 schema field changed
    • addedInput schema / properties / sort
      Added value: +{
+  "description": "copyable (default): by what a follower 1 slot behind made; own: by the wallet's own profit",
+  "enum": [
+    "copyable",
+    "own"
+  ],
+  "type": "string"
+}
  3. Added

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already cover the safety profile (read-only, idempotent), and the description goes well beyond them: it declares the tool free, the inclusion criteria (10+ SOL out, 1% net positive over 20+ coin-weeks, traded in the last ~20 days), the followability thresholds, and the withdrawal of the copyable ranking with the reason. It even previews what each row carries, which matters since there is no output schema.

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

Conciseness3/5

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

The core identity is front-loaded, but the long parenthetical about the Oct 31 withdrawal is convoluted ('at them, copying the best-scored wallets 1 slot behind lost money in all seven weeks tested') and consumes disproportionate space. The information is real, yet the phrasing could be compressed without losing the warning.

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

Completeness5/5

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

With no output schema, the description carries the return-value burden and does so: each wallet comes with why it qualified, SOL in and out, its coins, and recent pace metrics. Combined with universe and ranking rules, an agent has everything needed to call it and interpret results.

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

Parameters4/5

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

Schema coverage is 100%, so baseline would be 3, but the description adds real meaning: it spells out followable's concrete thresholds (under 20 trades/day, median hold of 2+ minutes, under half fast trades) rather than the schema's vague 'wallets a copier can keep up with', and explains when sort=own is forced. It says nothing about limit, but the schema documents that fully.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States the specific resource and scope up front: the pump.fun wallet leaderboard ranked by each wallet's own profit. It explicitly distinguishes itself from pump.fun's own leaderboard ('which ranks recent profit') and points to wallet_records for per-wallet detail, so an agent can place it among siblings without opening a schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives a literal use-case list ('who should I copy trade, the best pump.fun traders, smart money wallets'), names the alternative it is not, and routes to wallet_records for full records. It also discloses that the follower ranking is currently withdrawn, which prevents an agent from selecting a mode that no longer produces useful results.

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

All pumpdata toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources