Skip to main content
Glama
pumpfun-claims-bot

pumpfun-claims-bot

by nirholas

get_token_trades

Fetches recent PumpFun token trade activity, including volume and buy/sell counts, to help assess current market participation for a given mint address.

Instructions

Fetch recent trade activity for a PumpFun token (volume, buy/sell counts)

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

Input Schema

NameRequiredDescriptionDefault
mintYesToken mint address

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.0.5
    • removedInput schema / additionalProperties
      Removed value: -false
  2. First observedv1.0.4

TDQS

B3.2/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 disclosure burden. It does add return-content context (volume, buy/sell counts) beyond the schema, but leaves the meaning of 'recent', the aggregation window, and any rate/limit behavior unstated.

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?

One short, front-loaded sentence with no filler. The parenthetical is slightly ambiguous about what the counts measure, but nothing is redundant.

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 simple one-parameter read tool with no output schema, this is close to adequate but not complete: the time window for 'recent', the units of 'volume', and the return shape are all left to inference. Adding one clause about the lookback window would close the gap.

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?

There is a single required parameter and schema description coverage is 100%, so the schema already explains 'mint' as a token mint address. The description contributes nothing further about format or acceptable values, so the baseline of 3 applies.

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 specific verb (Fetch) and resource (recent trade activity for a PumpFun token), which is enough to separate it from get_token_holders, get_token_info and get_pool_liquidity. It does not explicitly name or contrast a sibling, 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?

There is no guidance on when to prefer this over the other token tools (holders, info, liquidity) and no stated prerequisites. 'Recent' implies a time-bounded query but never defines the window or any exclusions.

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