Skip to main content
Glama
pumpfun-claims-bot

pumpfun-claims-bot

by nirholas

get_bundle_info

Detects whether a token launch was bundled by checking a mint address, helping identify a common scam indicator before trading or approving claims.

Instructions

Detect if a token launch was bundled (scam indicator)

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_bundle_info"
  }
}

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

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden. It doesn't state what 'bundled' means operationally, whether the result is a boolean or a scored report, how confident the detection is, or any latency/cost/auth considerations — all of which matter for a heuristic scam detector.

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 sentence with the key concept front-loaded and no filler. It is efficient rather than padded, though the brevity comes at the cost of specification rather than being maximally informative.

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?

With no annotations and no output schema, the description is the only source for what the tool returns, and it doesn't say whether the answer is a boolean flag, a risk score, or evidence about the launch. For a heuristic detection tool, an agent needs that to interpret results and decide follow-ups.

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?

Schema coverage is 100% and the single 'mint' parameter is fully described as 'Token mint address', so the schema does the heavy lifting. The description implies the mint refers to a launched token, which adds slight context, but nothing about formatting (base58 vs other) beyond the schema.

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?

The description names a specific verb ('detect') and a specific condition ('token launch was bundled') with a parenthetical framing it as a scam indicator. An agent can tell this is a bundle-detection/rug-risk tool rather than a general token lookup, though it never explicitly contrasts itself with siblings like get_token_info.

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 when-to-use or when-not-to-use guidance beyond the implicit 'scam indicator' framing. It doesn't say whether this should be called pre-trade, on any token, or only on freshly launched tokens, and it names no alternatives despite several token-analysis siblings existing.

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