Skip to main content
Glama

Solana PumpFun Paywall

pump_bonding_curve

Decode live Pump.fun bonding curve PDA reserves & graduation % (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_bonding_curve"
  }
}

Input Schema

NameRequiredDescriptionDefault
mintYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It does disclose real behavioral content (the call costs 0.005 SOL and reports live reserves plus a graduation percentage), but it never confirms the operation is a read, never mentions failure behavior for an unknown or non-Pump.fun mint, and never says whether results are cached.

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 compact clause that leads with the verb and packs the scope, cost, and returned fields into one line. The density of unexplained jargon costs it a point, but there is no filler.

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 one-parameter read tool with no output schema, the description is only minimally adequate: it names two returned quantities and a cost, but leaves the parameter's format and the failure cases undefined. An agent could call it, but would learn the return shape only by trying.

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?

The input schema has zero description coverage for the single required parameter, mint, and the description does not compensate by saying that this must be the token's mint address (or its expected format). The reader has to infer the parameter's meaning from the tool name 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?

Uses a specific verb ("Decode") with a specific resource ("Pump.fun bonding curve PDA reserves & graduation %"), which is enough to tell it apart from the sibling tools that scan, rug-check, or quote swaps. The purpose is clear but the phrasing is jargon-dense, with no explicit statement of what a caller gets back beyond two field names.

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?

The description never states when to use this tool instead of pump_koth_scan, pump_rug_check, or pump_swap_quote, nor does it give prerequisites such as the mint having to belong to a live Pump.fun token. The only usage-relevant signal is the implied 0.005 SOL cost, which is quotable but not framed as guidance.

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