Skip to main content
Glama

X1 launchpad

x1_launchpad
Read-onlyIdempotent

Free sample: https://apexfaucet.xyz/launchpad/ ($0.002). Tokens launched on the APEX launchpad. sort is new, hot or volume. Does not launch a token. Not advice. $0.002 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": "x1_launchpad"
  }
}

Input Schema

NameRequiredDescriptionDefault
sortNonew, hot or volume
limitNo1 to 30
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

A3.6/5.0
Behavior4/5

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

Annotations only declare readOnly/idempotent/non-destructive; the description adds substantial context they cannot convey: price, accepted payment rails (USDC on Arc, Base or Solana, XNT on X1), and the two-step terms-signing requirement before the paid call succeeds. It stops short of saying what a payment failure or an already-signed payload looks like, which is the remaining gap for a paid tool.

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

Conciseness3/5

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

Front-loading the free sample and the "Does not launch a token" caveat is good, but the text is a string of telegraphic fragments, repeats the $0.002 price twice, and buries the critical payment procedure at the end behind "Not advice." filler.

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

Completeness3/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 should clarify the shape of a result, but it never says what a successful response contains beyond implying a token list, nor what `limit` (1–30) does to it. The free-sample-versus-paid relationship is also left ambiguous, which matters because a wrong assumption triggers or avoids a real $0.002 charge.

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 schema already defines `sort`, `limit` and `payment`, and the description's "sort is new, hot or volume" only restates it. The added value is the payment lifecycle around the `payment` parameter — obtaining and signing terms on a first call, then passing the payload on a second — which the schema alone does not convey.

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?

"Tokens launched on the APEX launchpad" plus "Does not launch a token" tells the agent this is a read/listing of launchpad tokens, not a launch action. The weakness is the absence of an explicit verb (list/get) and no differentiation from the sibling tools `launchpad` and `launchpad_curve_plan`, which an agent must disambiguate on its own.

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

Usage Guidelines3/5

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

The description gives a concrete call sequence for the paid flow (call without `payment` for terms, sign with your own wallet, call again with `payment`) and an exclusion ("Does not launch a token"). However, there is no guidance on when to pick this over the sibling `launchpad` tool, and the free-sample URL versus the $0.002 per-call charge is never reconciled into a single rule.

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