Skip to main content
Glama

Solana PumpFun Paywall

pump_swap_quote

Compute constant-product Pump.fun buy/sell quote (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>",
      "side": "<side>",
      "amount": "<amount>"
    },
    "name": "pump_swap_quote"
  }
}

Input Schema

NameRequiredDescriptionDefault
mintYes
sideYes
amountYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.6/5.0
Behavior2/5

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

With no annotations, the description must carry the full behavioral burden. It discloses that the quote uses a constant-product model and mentions a 0.005 SOL figure, but it does not clarify whether this is a fee, whether the quote executes anything, how fresh the quote is, or what assumptions apply to the returned value.

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 a single front-loaded sentence with no filler. However, the parenthetical '(0.005 SOL)' is ambiguous, and the extreme brevity leaves little structure for an agent to rely on.

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

Completeness2/5

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

The tool has three required but undocumented parameters and no output schema. The description mentions the pricing model and a SOL figure but does not provide enough context about inputs, quote semantics, or return behavior for an agent to invoke it confidently.

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

Parameters1/5

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

Schema description coverage is 0%, so the description must compensate by explaining the three required parameters. It does not explain what mint should contain, what unit or format amount expects, or how side affects the result beyond the schema's own enum.

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 gives a specific verb and resource: compute a Pump.fun buy/sell quote using a constant-product model. It is clear what the tool does, but it does not explicitly distinguish itself from siblings such as pump_bonding_curve, which may also produce pricing-related information.

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 implies the tool is used for quoting a buy or sell, but it gives no explicit when-to-use or when-not-to-use guidance. It also does not name alternatives or explain when another sibling tool would be more appropriate.

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