Skip to main content
Glama

My MCP Server

pump-fun-bonding-curve

Live Solana Mainnet pump-fun-bonding-curve ($0.10 USDC via x402 v2 PAYMENT-SIGNATURE header)

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "pump-fun-bonding-curve"
  }
}

Input Schema

NameRequiredDescriptionDefault
mintNo
targetWalletNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2/5.0
Behavior2/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 earn credit for disclosing a concrete behavioral fact an agent could not otherwise know — a $0.10 USDC charge paid through an x402 v2 PAYMENT-SIGNATURE header — but it omits whether the call is read-only, what happens on payment failure, and what the response contains.

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

Conciseness2/5

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

The single parenthetical line is short but under-specified rather than concise; it front-loads payment mechanics ahead of what the tool returns. Space saved by brevity is space an agent must spend inferring purpose.

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?

For a paid data-fetch tool with zero annotation coverage, no output schema, and two undocumented parameters, the description leaves the essential contract — what you get back for your $0.10 and under what conditions — unstated. The payment/auth detail is welcome but not enough to make the definition self-sufficient.

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?

With two parameters at 0% schema description coverage, the description needs to explain 'mint' and 'targetWallet' and does not. The names are somewhat self-descriptive, but nothing clarifies whether mint is required, what targetWallet scopes (filtering? payment payer?), or whether omitting both returns an aggregate.

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

Purpose2/5

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

The text names a resource ('pump-fun-bonding-curve') and a network ('Live Solana Mainnet') but supplies no verb, so what the tool actually does — read bond curve state, quote a price, fetch reserves — must be guessed from the name. It largely restates the tool name with a network qualifier added.

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?

There is no statement of when to call this versus siblings such as raydium-swap-automator or orca-whirlpool-scanner, and no prerequisites or exclusions. The only implied guidance is the word 'Live', hinting at real-time rather than historical data, which is too thin to route an agent reliably.

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