Agent Einstein — Crypto & Market Intelligence

Launchpad Radar

get_launchpad_radar

Read-onlyIdempotent

Tokens that just migrated off a bonding curve onto a DEX, with holder-distribution forensics: what share the dev, snipers, insiders and bundler wallets hold, plus wash-trading tags. Covers Pump.fun, Bonk, Raydium, Meteora, Four.meme, Flap and others through one feed. Use when asked about new launches, fresh memecoins, or whether a launch is bundled.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`limit`	No	Rows to return (1-15).

Output Schema

TableJSON Schema

Name	Required	Description
`rows`	No	Launchpad tokens approaching or past migration.
`chain`	No	Chain the screen ran on.
`object`	No	Always "launchpad-radar".
`reason`	No	Why the payload is absent, when `available` is false.
`available`	No	False when this call has no data — a snapshot that is not warm yet, a domain switched off, or an argument that was rejected. NOT an error, and NOT a statement about the market.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 3, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "properties": {
+    "available": {
+      "description": "False when this call has no data — a snapshot that is not warm yet, a domain switched off, or an argument that was rejected. NOT an error, and NOT a statement about the market.",
+      "type": "boolean"
+    },
+    "chain": {
+      "description": "Chain the screen ran on."
+    },
+    "object": {
+      "description": "Always \"launchpad-radar\"."
+    },
+    "reason": {
+      "description": "Why the payload is absent, when `available` is false.",
+      "type": "string"
+    },
+    "rows": {
+      "description": "Launchpad tokens approaching or past migration.",
+      "items": {
+        "additionalProperties": true,
+        "properties": {
+          "bundlerHoldingPct": {
+            "description": "Share held through bundlers."
+          },
+          "chainId": {
+            "description": "EVM chain id."
+          },
+          "contractAddress": {
+            "description": "Token contract."
+          },
+          "createTime": {
+            "description": "Creation time."
+          },
+          "devAddress": {
+            "description": "Deployer address."
+          },
+          "devPosition": {
+            "description": "Deployer position size."
+          },
+          "devSellPct": {
+            "description": "Share of the deployer position already sold."
+          },
+          "holders": {
+            "description": "Holder count."
+          },
+          "holdersDevPct": {
+            "description": "Share held by the deployer."
+          },
+          "holdersInsiderPct": {
+            "description": "Share held by insiders."
+          },
+          "holdersSniperPct": {
+            "description": "Share held by snipers."
+          },
+          "holdersTop10Pct": {
+            "description": "Share held by the top 10 holders."
+          },
+          "liquidityUsd": {
+            "description": "Pool liquidity."
+          },
+          "marketCapUsd": {
+            "description": "Market cap in USD."
+          },
+          "migrateStatus": {
+            "description": "Migration status."
+          },
+          "name": {
+            "description": "Token name."
+          },
+          "newWalletHoldingPct": {
+            "description": "Share held by wallets created around launch."
+          },
+          "priceChangePct": {
+            "description": "Percentage price change over the period."
+          },
+          "priceUsd": {
+            "description": "Price in USD."
+          },
+          "progressPct": {
+            "description": "Bonding-curve progress toward migration."
+          },
+          "protocol": {
+            "description": "Launchpad protocol."
+          },
+          "socials": {
+            "additionalProperties": true,
+            "description": "Links the token publishes."
+          },
+          "symbol": {
+            "description": "Token symbol."
+          },
+          "tagDevWashTrading": {
+            "description": "Deployer wash-trading flag."
+          },
+          "tagInsiderWashTrading": {
+            "description": "Insider wash-trading flag."
+          },
+          "volumeUsd": {
+            "description": "Period volume."
+          }
+        }
+      },
+      "type": "array"
+    }
+  },
+  "type": "object"
+}

AddedAug 21, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already cover read-only, idempotent, and non-destructive behavior. The description adds meaningful context beyond that: it reveals the tool's analytical content, multi-launchpad coverage through 'one feed,' and the specific wallet categories included in the forensics. This is useful behavioral context without contradicting the annotations.

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

Conciseness5/5

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

The description is tightly structured: the first sentence states what the tool returns, the second covers supported launchpads, and the third gives the usage cue. Every sentence earns its place with no repetition or filler.

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

Completeness5/5

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

With only one optional parameter fully documented in the schema, an output schema present, and annotations covering safety, the description provides enough context for an agent to select and invoke the tool correctly. Nothing critical is missing.

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?

The input schema has 100% coverage for the single `limit` parameter, which is already described as 'Rows to return (1-15).' The description does not add parameter-level detail, so the baseline of 3 is appropriate.

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?

The description clearly identifies the resource: tokens that just migrated off a bonding curve onto a DEX, with holder-distribution forensics and wash-trading tags. It distinguishes itself from siblings through its specific focus on migration, bundling forensics, and multi-launchpad coverage, though it lacks an explicit verb like 'list' or 'fetch.'

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 explicitly states when to use the tool: 'Use when asked about new launches, fresh memecoins, or whether a launch is bundled.' It does not mention when not to use it or name alternatives like scan_launchpads, so it stops short of full 5-level guidance.

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

All Agent Einstein — Crypto & Market Intelligence tools Inspect

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.