Skip to main content
Glama

Solana PumpFun Paywall

pump_rug_check

Audit top-10 holder concentration & same-slot sniper bundles (0.005 SOL)

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

Input Schema

NameRequiredDescriptionDefault
mintYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.8/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It usefully discloses a per-call cost of 0.005 SOL, but says nothing about what the audit returns, whether the fee is charged on failure, rate limits, or how 'sniper bundles' are detected. For a paid analysis tool with zero annotation coverage this is a significant gap.

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 with no wasted wording, and the cost is placed inline where it is easy to spot. It is efficient, though arguably over-terse for the amount of information an agent needs.

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?

With one param, no annotations, and no output schema, the definition covers the core purpose and the price but omits what the parameter is and what the response looks like. Adequate to recognize the tool, not quite enough to invoke 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?

Schema coverage is 0% and the single parameter 'mint' is never explained in the description. It is only inferable from the pump_ prefix that 'mint' is a token mint address; no format, chain, or validity constraints are given.

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 (audit) and concrete resources (top-10 holder concentration, same-slot sniper bundles), which is more informative than a generic 'check token' phrasing and is clearly distinct from the sibling tools (bonding curve, KOTH scan, swap quote). It stops short of naming a sibling or saying explicitly that it targets a pump.fun token mint.

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 guidance, no prerequisites, and no alternatives named. The '(0.005 SOL)' hint implies a paid pre-trade safety check but never states when an agent should call this versus pump_bonding_curve or pump_koth_scan.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources