Skip to main content
Glama

Launchpad

launchpad

Launch a token on X1, or read what has been launched. Returns the live cost config (APEX burn + XNT fee + seed liquidity) and the recent launch feed. The build endpoints return unsigned transactions you sign yourself.

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

Input Schema

NameRequiredDescriptionDefault
mintNoOptional mint for detail on one launched token.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose real behavior: the return payload includes live cost config (APEX burn, XNT fee, seed liquidity) and the recent launch feed, and build endpoints emit unsigned transactions the caller signs. It omits prerequisites for launching, whether the operation costs funds, and what distinguishes the build path from the read path — meaningful gaps for a write-capable tool.

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?

Three short sentences, front-loaded with the action and followed by return-shape and transaction-signing details. Nothing is padded, though the sentence about build endpoints could be tied more explicitly to the launch mode.

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?

For a dual-mode tool with no annotations and no output schema, the description covers the return payload reasonably but leaves the mode-switching logic, fund/cost prerequisites, and failure behavior unexplained. Adequate to attempt a call, not 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 `mint` parameter is documented in the schema as selecting detail on one launched token. The description never mentions `mint` or explains how providing it changes the response, so it adds nothing beyond the schema; baseline 3 applies for a one-parameter tool with full coverage.

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?

States a specific verb and resource ('Launch a token on X1') plus a second read mode, so the agent immediately knows what the tool covers. It does not name which sibling to prefer for the read side (e.g. base_launch_feed, arc_fresh_launches), so sibling differentiation is only partial.

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 implies two modes — launch versus read the feed — but never states which input selects which mode, nor when to reach for this instead of the many other launch/feed tools in the sibling list. Usage is inferable rather than explicit.

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