Skip to main content
Glama
pumpfun-claims-bot

pumpfun-claims-bot

by nirholas

get_pool_liquidity

Fetches PumpSwap AMM pool liquidity for a graduated token by mint address, helping you check available liquidity before trading or analyzing claims.

Instructions

Fetch PumpSwap AMM pool liquidity for a graduated token

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>"
    },
    "name": "get_pool_liquidity"
  }
}

Input Schema

NameRequiredDescriptionDefault
mintYesToken mint address
usdMarketCapNoCurrent USD market cap (for context)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.0.5
    • removedInput schema / additionalProperties
      Removed value: -false
  2. First observedv1.0.4

TDQS

B3.2/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 of behavioral disclosure, and it discloses very little. 'Fetch' implies a read, but there is no statement of return units (SOL vs. USD), behavior when no pool exists, latency or rate limits, or whether usdMarketCap changes what is computed.

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?

A single front-loaded sentence with zero filler; the core purpose arrives immediately. It is efficient but arguably over-trimmed, since a short second clause on units or the pool-missing case would have cost little.

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

Completeness3/5

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

There is no output schema and no annotations, so the description is the only place an agent can learn what comes back and under what conditions. It covers the identity of the operation but leaves the return shape, unit basis, and the role of the optional context parameter unaddressed.

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

Parameters3/5

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

Schema description coverage is 100%, so both parameters are already documented in the input schema, and the description adds nothing about either one. In particular it leaves unexplained why a 'context' parameter (usdMarketCap) exists and how it affects the liquidity result, which is the one place prose could have added value beyond the schema.

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?

States a specific verb ('Fetch') and resource ('PumpSwap AMM pool liquidity') and scopes it to a 'graduated token', which is meaningfully narrower than the generic token tools among the siblings. It stops short of naming a sibling or explicitly contrasting itself with get_token_info or get_token_trades, so it earns a 4 rather than a 5.

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

Usage Guidelines3/5

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

The phrase 'for a graduated token' implies a precondition for use (the token must have completed bonding-curve graduation to PumpSwap), which is a real implied usage signal. However, it never says what to do for a non-graduated token, nor does it point to any alternative tool, so guidance is only implied.

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