Skip to main content
Glama
Sign In

pumpdata

by fun.pumpdata
OverviewDiscussionsAdmin

launches_since

Read-onlyIdempotent

Free. Every pump.fun launch after a moment in the last 24 hours, oldest first: each with its deployer's record before it (launches, graduations, seconds since its last launch) and the first-10-second bundle; launches newer than the hourly fill come within the minute (source live, bundle not yet read). For: what launched just now, new coins from devs with a record, watch new launches. Poll with t = next_since; call check_coin only for the coins worth a look.

Input Schema

NameRequiredDescriptionDefault
tNounix seconds, within the last 24 hours; launches after it are listed. Left out: the last ten minutes
checkNotrue: each launch also gets checks[i]: the first 10 seconds' buy share, whether the deployer has sold, same-ticker launches in the hour, market cap now
limitNolaunches to return; default 500
deployerNoonly this deployer wallet's launches (base58)
min_launchesNoonly launches by deployers with this many launches before (e.g. 20: the serial deployers)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / check
      Added value: +{
+  "description": "true: each launch also gets checks[i]: the first 10 seconds' buy share, whether the deployer has sold, same-ticker launches in the hour, market cap now",
+  "type": "boolean"
+}
  2. Changed2 schema fields changed
    • addedInput schema / properties / deployer
      Added value: +{
+  "description": "only this deployer wallet's launches (base58)",
+  "type": "string"
+}
    • addedInput schema / properties / min_launches
      Added value: +{
+  "description": "only launches by deployers with this many launches before (e.g. 20: the serial deployers)",
+  "minimum": 1,
+  "type": "integer"
+}
  3. Added

TDQS

A4.5/5.0
Behavior5/5

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

Goes well past the annotations by disclosing freshness/latency ('launches newer than the hourly fill come within the minute (source live, bundle not yet read)'), result ordering (oldest first), and that the call is free. These are exactly the operational traits an agent needs to decide polling cadence and whether enrichment fields are trustworthy.

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?

Front-loaded and waste-free in intent, but the sentences are heavily packed — the parenthetical '(launches, graduations, seconds since its last launch)' and 'Free.' as a fragment take parsing effort. Nothing is redundant, though; trimming would cost real information.

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 five optional params and no output schema, the description carries the return-shape burden and does so partially: order, enrichment fields and freshness are covered, but the fill-in of check-style metrics is not spelled out, and nothing is said about behavior on empty ranges or the 24-hour window boundary.

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?

Schema coverage is 100%, so the baseline is 3, but the description adds the cursor contract that the input schema cannot express: the returned next_since is what should be fed back into t. It stays silent on the `check` vs check_coin naming overlap, which is the one place extra clarity would have helped.

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

Purpose5/5

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

States a specific resource and scope: 'Every pump.fun launch after a moment in the last 24 hours, oldest first', plus what each row carries (deployer record, first-10-second bundle). An agent can tell this is a paged, raw launch feed rather than a per-coin lookup (check_coin) or a stats/odds tool.

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?

Explicit use cases ('what launched just now', 'new coins from devs with a record', 'watch new launches') and an explicit routing rule: poll with t = next_since and reserve check_coin for coins worth a look. What is missing is differentiation from close siblings like live_events, replay or today_live, which an agent must still guess between.

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

All pumpdata toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources