Skip to main content
Glama

New token launches (x402)

token_launches_feed

Read-onlyIdempotent

$0.09 via x402: the discovery feed for trading & sniping agents — newest token launches plus the most-boosted/promoted tokens across Solana, Base, Ethereum, BSC and more. Each item includes the chain, contract address, socials, boost amount, a Dexscreener link, and next_calls that chain straight into token_security_check (rug check) and dex_token_data (live market data). Poll this on a loop to find candidates, then verify and price them. Live from Dexscreener.

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

Input Schema

NameRequiredDescriptionDefault
chainNooptional filter: solana|base|ethereum|bsc (default all chains)
limitNo1-30, default 15
x_paymentNox402 payment payload (base64) to settle this call; omit to receive the payment terms first

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnly/openWorld/idempotent, yet the description still adds real value: a $0.09 x402 price, the payment handshake ('omit x_payment to receive the payment terms first'), the upstream data source (Dexscreener), and per-item return fields including a next_calls hand-off. It does not cover failure modes, rate limits, or freshness/refresh cadence beyond 'live', so it stops short of a 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?

Cost and purpose are front-loaded in the first clause, and the three sentences map cleanly to what-it-is, what-you-get, how-to-use. Slightly dense and leans on promo phrasing ('sniping agents', 'and more', 'Live from Dexscreener') that is not strictly load-bearing.

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 no output schema, the description carries the return-shape burden and does so by enumerating chain, contract address, socials, boost amount, Dexscreener link, and next_calls. It also closes the payment/prerequisite loop, so an agent has everything needed to call it correctly on a no-parameter-required tool.

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 description coverage is 100% and each parameter (chain enum-ish filter, limit range, x_payment base64 payload) is already documented in the schema, so the baseline applies. The description reinforces the payment parameter's purpose and the returned next_calls field, but adds no syntax, defaults, or edge cases the schema lacks.

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?

A specific verb-and-resource statement: 'the discovery feed for trading & sniping agents — newest token launches plus the most-boosted/promoted tokens' across named chains. It also states what it is NOT by pointing at token_security_check and dex_token_data as downstream verification/pricing tools, so an agent can distinguish it from siblings without opening schemas.

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

Usage Guidelines5/5

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

Explicit workflow guidance: 'Poll this on a loop to find candidates, then verify and price them,' with the two sibling tools named and assigned their roles (rug check, live market data). It tells the agent both when to call this tool and what to call next, which is exactly the routing an agent needs.

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