Skip to main content
Glama

three.ws pump.fun MCP

by io.github.nirholas

Swap Quote (Read-Only)

pumpfun_quote_swap
Read-only

Read-only price quote for a pump.fun AMM (PumpSwap) swap. No signing or tx sending. One of inputMint/outputMint must be wSOL (So11111111111111111111111111111111111111112). Only GRADUATED coins have an AMM pool; for a coin still on its bonding curve use get_bonding_curve instead. Pricing runs on the pool effective quote reserves (quote vault balance + pool.virtual_quote_reserves); the base side is the raw base vault balance. Returns amountOut, priceImpactBps, route, expiresAtMs, plus the reserves the quote was computed from so the number can be reproduced.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
networkNomainnet
amountInYesInput amount in raw base units (lamports for SOL).
inputMintYesInput token mint (base58).
outputMintYesOutput token mint (base58).
slippageBpsNoSlippage tolerance in basis points (default 100 = 1%).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
routeYesAMM pool address the quote routes through (base58)
amountOutYesExpected output amount in raw base units
expiresAtMsYesEpoch ms after which the quote is stale
base_reserveNoRaw base vault balance. Unchanged by the virtual-reserve rollout.
quote_reserveNoRaw quote vault balance, before virtual reserves are added.
priceImpactBpsYesPrice impact in basis points
virtual_quote_reservesNoPool.virtual_quote_reserves. Quote-side liquidity the pool carries outside its vault. 0 on non-launchpad pools.
effective_quote_reserveNoquote_reserve + virtual_quote_reserves. This is what the quote is priced against.

TDQS

A4.8/5.0
Behavior5/5

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

The description adds significant behavioral context beyond the readOnlyHint annotation, explaining the pricing computation (reserves used), confirming no signing/tx sending, and listing output fields (amountOut, priceImpactBps, route, expiresAtMs, reserves). No contradiction with annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is four sentences, front-loaded with the core purpose, followed by constraints, alternative tool, pricing details, and outputs. Every sentence adds value with no redundancy.

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?

Given the tool's complexity (5 parameters, output schema exists), the description covers key aspects: read-only nature, constraints, alternative tool, and output fields. It could briefly mention slippageBps usage, but schema covers it, so minor gap.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 80%, and the description adds a crucial constraint not in the schema: 'One of inputMint/outputMint must be wSOL.' It repeats the unit clarification for amountIn but does not elaborate further; overall it adds meaningful value.

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 provides a read-only price quote for a pump.fun AMM swap, with a specific verb ('quote') and resource ('swap'). It distinguishes itself from the sibling tool get_bonding_curve by specifying that only graduated coins with an AMM pool apply.

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 tells when to use this tool (for AMM swaps) and when not to (use get_bonding_curve for coins on bonding curve). It also states the constraint that one of inputMint/outputMint must be wSOL, guiding correct invocation.

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