Skip to main content
Glama

three.ws pump.fun MCP

by io.github.nirholas

Bonding Curve

get_bonding_curve
Read-only

Bonding curve analysis: real reserves, virtual reserves, and graduation progress (on-chain). Pre-graduation only: these reserves come from the pump program bonding-curve account, not from a PumpSwap pool. Pump renamed the quote-side fields on-chain (real_sol_reserves -> real_quote_reserves, virtual_sol_reserves -> virtual_quote_reserves) once a non-SOL quote asset became possible; the response keys below keep their original names and are still denominated in SOL, because the curve quote_mint is the SOL default on every coin created to date. Once complete=true the curve is retired and pricing moves to the PumpSwap pool, so use pumpfun_quote_swap from that point on.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
mintYes
networkNomainnet

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
mintYes
networkYes
completeYestrue once the curve has graduated
solReservesYesReal quote reserves in SOL (4-decimal string). On-chain field: real_quote_reserves.
tokenReservesYesReal token reserves (raw base units)
graduationPercentYes0–100 graduation progress
virtualSolReservesYesVirtual quote reserves (lamports). On-chain field: virtual_quote_reserves (u64). Spot price = virtual_quote_reserves / virtual_token_reserves. Distinct from the identically-named PumpSwap Pool.virtual_quote_reserves (an i128), which applies only after graduation.
virtualTokenReservesYesVirtual token reserves (raw base units)

TDQS

A4.4/5.0
Behavior5/5

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

The description adds significant context beyond annotations: explains data source (pump program bonding-curve account), field renames, and that responses are in SOL. No contradictions with annotations (readOnlyHint, etc.).

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?

The description is moderately concise, conveying necessary context in a well-structured paragraph. Could be slightly more terse, but front-loads purpose well.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With an output schema present, the description adequately covers nuances like data source and graduation behavior. Minor gap: doesn't mention pagination or size limits, but overall complete for the tool's complexity.

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 description coverage is 0%. The description does not explain the 'mint' or 'network' parameters, leaving the agent without semantic guidance for parameter usage beyond the schema field names.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool does bonding curve analysis: real reserves, virtual reserves, and graduation progress on-chain. It distinguishes from the post-graduation sibling tool pumpfun_quote_swap, making the purpose specific and unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explicitly states 'Pre-graduation only' and instructs to use pumpfun_quote_swap once complete=true, providing clear when-to-use and when-not-to-use guidance with an alternative.

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

All three.ws pump.fun MCP toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.5/5.0
Disambiguation4/5

Most tools have distinct purposes, but get_coin_intel and get_oracle_conviction overlap in providing intelligence signals; descriptions help differentiate but still may cause confusion.

Naming Consistency3/5

Naming patterns are mixed: some use snake_case (get_bonding_curve), others use camelCase (sns_reverseLookup), and kol_leaderboard lacks a prefix that others like pumpfun_ have.

Tool Count4/5

19 tools cover a broad range of pump.fun functionality, from token details to claims and social analysis; the count feels appropriate for the scope.

Completeness5/5

The tool set covers virtually all core aspects of pump.fun ecosystem: token info, intelligence, trading, claims, AMM quotes, metadata upload, SNS, and social sentiment, with no obvious gaps.

Resources