three.ws pump.fun MCP

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. A v3 buy that empties the curve completes it and buys the rest through a synthetic migration, priced on the reserves the PumpSwap pool will open with, so a large final buy is not capped at realTokenReserves. Once complete=true the curve is retired and pricing moves to the PumpSwap pool, so use pumpfun_quote_swap from that point on. Use this to read graduation progress or the curve spot price of a coin that has not graduated yet.

Input Schema

Name	Required	Description	Default
`mint`	Yes
`network`	No		mainnet

Output Schema

Name	Required	Description
`mint`	Yes
`network`	Yes
`complete`	Yes	true once the curve has graduated
`solReserves`	Yes	Real quote reserves in SOL (4-decimal string). On-chain field: real_quote_reserves.
`tokenReserves`	Yes	Real token reserves (raw base units)
`graduationPercent`	Yes	0–100 graduation progress
`virtualSolReserves`	Yes	Virtual 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.
`virtualTokenReserves`	Yes	Virtual token reserves (raw base units)

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedJul 20, 2026

changedOutput schema / properties / solReserves / description

Previous value: -"Real SOL reserves in SOL (4-decimal string)"New value: +"Real quote reserves in SOL (4-decimal string). On-chain field: real_quote_reserves."

changedOutput schema / properties / virtualSolReserves / description

Previous value: -"Virtual SOL reserves (lamports)"New value: +"Virtual 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."

First observedJun 13, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Annotations already declare readOnly/openWorld/non-destructive, and the description adds substantial context beyond them: the on-chain source account (pump program bonding-curve account, not a PumpSwap pool), the field-renaming caveat, SOL denomination, and the v3 buy edge case where a final buy is not capped at realTokenReserves. This is exactly the kind of behavioral disclosure structured fields cannot carry.

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?

Front-loaded with the core purpose, then progressively adds caveats. It is dense and the field-renaming paragraph borders on tangent for tool selection, but the content is mostly relevant and the sizing is defensible for a tool with tricky semantics.

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

Completeness5/5

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

An output schema exists so return values need not be described, and the description still supplies the interpretive context (reserve naming, denomination, graduation transition) an agent needs. Nothing essential to correct invocation is missing.

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% (2 params, neither documented). The description never explains what 'mint' or 'network' mean or their expected format/values, so it fails to compensate for the coverage gap despite strong surrounding domain context.

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?

States a specific verb+resource ('bonding curve analysis: real reserves, virtual reserves, and graduation progress') and explicitly scopes it to pre-graduation coins. It also distinguishes itself from the pumpfun_quote_swap sibling, so an agent can tell them apart without opening a schema.

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?

Explicit when-to-use ('read graduation progress or the curve spot price of a coin that has not graduated yet') and when-not-to-use ('once complete=true ... use pumpfun_quote_swap from that point on'). The alternative is named and the selecting condition is given.

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 tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.