Skip to main content
Glama

Solana Signal

Newest pump.fun launches (preview)

pump_new_launches
Read-only

Preview of the 10 newest pump.fun token launches collected live 24/7: mint, name, symbol, creator, dev buy (SOL and % supply), creator launches in last 24h (serial-rugger detection). Paid endpoint returns up to 200 with filters. Free tier 20/day per IP.

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_new_launches"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, but the description adds real value beyond them: item count (10), the exact field set returned (mint, name, symbol, creator, dev buy SOL/%, creator launches in 24h), live 24/7 collection, and a concrete 20/day per-IP rate limit. It doesn't state latency/caching or whether the 10 are deduplicated, so not a full 5.

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 sentences, front-loaded with the core identity, then the field list and tier limits. The parenthetical '(serial-rugger detection)' and 'collected live 24/7' are dense but earn their place as behavioral and interpretive context; slight over-packing in one sentence keeps it off a 5.

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?

With no output schema, the description must carry return-value information, and it does by enumerating the returned fields and their key signals (dev buy in SOL and % supply, 24h creator launch count). It lacks field types/units detail and pagination behavior, which keeps it below 5.

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?

Zero required parameters gives a baseline of 4, and the description reinforces it by making clear this endpoint takes no filters while the paid variant does. Nothing further is needed on parameter meaning for a parameterless preview call.

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?

It states a specific verb+resource+scope ('Preview of the 10 newest pump.fun token launches'), which is unambiguous against the sibling set (token_risk, token_prices, tx_explain). It only implicitly differentiates from a fuller/paid variant ('Paid endpoint returns up to 200') without naming the sibling tool that provides it.

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

Usage Guidelines4/5

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

It gives clear context for when this fits: a no-parameter preview of 10 launches, with free-tier throughput of 20/day per IP and a pointer that a paid endpoint offers up to 200 with filters. It stops short of an explicit 'use X when you need filtering/history' routing sentence naming an alternative.

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