Skip to main content
Glama
pump.fun MCP Server

pump.fun MCP Server

by blixtrade

screen_tokens

Screen live Solana memecoins by liquidity, market cap, volume, age, and 1h change; apply source and threshold filters to identify tokens for research.

Instructions

Screen live Solana memecoins (trending, new or boosted) by liquidity, market cap, volume, age and 1h change. Ages are in minutes.

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": "screen_tokens"
  }
}

Input Schema

NameRequiredDescriptionDefault
sortNovol
limitNo
sourceNotrending
pumpOnlyNo
maxAgeMinutesNo
minChange1hPctNo
maxMarketCapUsdNo
minLiquidityUsdNo
minMarketCapUsdNo
minVolume24hUsdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.7/5.0
Behavior2/5

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

No annotations exist, so the description carries the full behavioral burden, yet it only implies that results are a live snapshot. It says nothing about ordering defaults, result shape, pagination beyond `limit`, rate limits, auth, or whether screening hits a cached or real-time feed — all material for a 10-parameter discovery tool.

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?

Two short sentences, front-loaded with purpose and followed by the one non-obvious unit clarification. Nothing is wasted, though the brevity is partly under-specification rather than discipline.

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?

Ten optional parameters, zero schema descriptions, no annotations, and no output schema means the description is the only source of truth — and it explains far too little. An agent cannot predict result shape, sort semantics, or what `pumpOnly` filters without guessing.

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%, so the description must compensate for all 10 parameters. It names several filter dimensions (liquidity, market cap, volume, age, 1h change) and clarifies that ages are in minutes, which helps `maxAgeMinutes` and `sort=age`; however `sort`, `limit`, `pumpOnly`, `minVolume24hUsd`, and the multi-timeframe change sorts (chg5m/chg24h) are left entirely undocumented.

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 and resource — 'Screen live Solana memecoins' — and names the three source categories (trending, new, boosted) that map to the `source` enum. It does not explicitly differentiate itself from siblings like token_info or rug_check, so an agent must infer that this is the bulk-listing/screening tool.

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 when-to-use or when-not-to-use guidance and no named alternative. An agent gets no help deciding between screening a list here versus fetching a single token via token_info or a safety check via rug_check; usage is only implied by the verb 'screen'.

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