Skip to main content
Glama
pump.fun MCP Server

pump.fun MCP Server

by blixtrade

wallet_trades

Fetches recent memecoin buys and sells for a Solana wallet from on-chain transactions, with a configurable count of 5 to 100 transactions.

Instructions

Recent memecoin buys and sells by a Solana wallet, read from its on-chain transactions. Slow on the public RPC (about one transaction per second).

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": {
      "wallet": "<wallet>"
    },
    "name": "wallet_trades"
  }
}

Input Schema

NameRequiredDescriptionDefault
walletYesSolana wallet address.
transactionsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.1/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 burden, and it does add real value: the data provenance (read from on-chain transactions) and an explicit performance characteristic (~1 transaction per second on the public RPC). It omits other behavioral facts an agent needs, such as ordering of results, behavior for invalid or inactive wallets, and whether non-memecoin swaps are excluded.

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?

Two short sentences, zero filler. The core purpose is front-loaded and the operational caveat follows immediately, so an agent can scan it in one pass.

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 two-parameter read tool with no annotations and no output schema, the description covers purpose, data source, and latency but leaves the `transactions` parameter and the shape of a returned trade unexplained. It is adequate to start a call but not complete for interpreting results.

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?

Schema coverage is only 50%: `wallet` is documented in the schema, but `transactions` has no description beyond its default of 25 and 5-100 bounds, and the description never explains what it controls. 'Recent' only loosely implies a count limit, leaving the agent to infer the parameter's meaning from the schema alone.

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?

States a concrete resource (memecoin buys and sells) scoped to a specific subject (a Solana wallet) and a specific data source (its on-chain transactions). 'Recent' sets scope. It stops short of naming a sibling such as whale_trades, so differentiation is inferred rather than stated.

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?

There is no explicit when-to-use or when-not-to-use guidance and no alternative tool is named, even though whale_trades sits in the sibling set. The RPC latency note is a performance caveat, not routing guidance, so the agent must guess which tool to pick for a given wallet-trade question.

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