Skip to main content
Glama

Base launch feed

base_launch_feed

New token launches on Base with a real sell test: every new Base pool (Uniswap v2/v3/v4, Aerodrome) found minutes after it opens, each token graded BASED, MID, COOKED or RADIOACTIVE from a buy and full sell simulated in one block (UNTESTED when no pool can be simulated). Poll with since= so you pay only for new rows; optional limit and min_liq. A feed older than 15 minutes is refused before payment. Facts, never advice. $0.01 per call over x402 (USDC on Arc, Base or Solana, or XNT on X1). Call once without payment for the terms, sign them with your own wallet, call again with payment.

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

Input Schema

NameRequiredDescriptionDefault
paymentNoa signed x402 payment (the base64 payload you would put in PAYMENT-SIGNATURE). Pass it and the purchase completes inside this tool call.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior5/5

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

With no annotations, the description carries the full burden and does so well: it discloses the buy-and-full-sell simulation, the UNTESTED fallback, the 15-minute stale-feed refusal before payment, per-call cost, accepted payment assets, and the payment handshake. This is unusually rich behavioral context for invoking a paid feed correctly.

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?

The description front-loads the purpose, then packs in grading logic, polling guidance, staleness rules, and payment mechanics in a reasonably ordered way. It is dense but mostly purposeful; minor marketing-style phrasing and references to parameters absent from the schema slightly reduce crispness.

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?

For a complex paid feed with no annotations or output schema, it covers the data meaning, grading categories, polling, staleness, and payment flow well enough to invoke. It still does not define the exact return shape or fields, and it references inputs not present in the schema, so it is complete enough but not fully complete.

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 coverage is 100% and the single actual parameter, payment, is clearly explained as a signed x402 payload plus the first-call/second-call flow. However, the description also instructs the agent to use since, limit, and min_liq even though those inputs are absent from the schema, which can mislead invocation; the high schema coverage supports the baseline 3.

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 feed for new token launches on Base and distinguishes it through a real sell test with token grades (BASED, MID, COOKED, RADIOACTIVE). That is more specific than a generic launch-feed description and separates it from siblings such as base_fresh_launches.

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?

Explains the polling flow with since=<nextSince>, optional limit and min_liq, stale-feed refusal before payment, and the two-step x402 flow: call without payment for terms, sign with a wallet, then call again with payment. It does not explicitly compare against alternatives or state when not to use it, so it falls short of a 5.

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