Skip to main content
Glama

POPULAR (Sui memecoin launchpad)

Build a token launch step (unsigned)

build_launch_step
Read-only

Launching a token on a SUI bonding curve takes three transactions, each signed and executed before the next: step publish (name, symbol, description, iconUrl), then register (publishDigest), then create (publishDigest, devBuy SUI, feeMode 0 Creator / 1 Buyback & Burn / 2 Holders / 3 Balanced, website, x, telegram). Launch fee 1 SUI plus gas.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "sender": "<sender>",
      "step": "<step>"
    },
    "name": "build_launch_step"
  }
}

Input Schema

NameRequiredDescriptionDefault
xNo
nameNo
stepYes
devBuyNoSUI for the creator's first buy (optional).
senderYesA Sui address, 0x and 64 hex digits.
symbolNo2-10 letters or digits.
feeModeNo
iconUrlNohttps:// image URL.
websiteNo
telegramNo
descriptionNo
publishDigestNoDigest of the executed publish transaction.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Beyond the annotations, the description discloses the multi-transaction dependency chain, the required fee (1 SUI plus gas), and the per-step prerequisites such as publishDigest. It also makes clear the output is unsigned despite being a launch operation, which explains the readOnlyHint. It omits anything about return payload shape, but no output schema exists to cover that.

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?

A single dense sentence front-loads the three-step workflow and then the per-step inputs, with the fee appended. It is efficient, though the deeply nested parenthetical list makes it harder to scan than a short bulleted sequence would be.

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 12-parameter, multi-stage build tool with no output schema, the definition covers sequencing, required inputs, enum meanings, and the launch fee — enough to call it correctly. The main remaining gap is that it never says what the tool returns (presumably an unsigned transaction payload) or whether that payload must be passed forward.

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?

With only 42% schema description coverage across 12 parameters, the description compensates well by grouping fields by step and decoding the feeMode enum (0 Creator, 1 Buyback & Burn, 2 Holders, 3 Balanced) and devBuy's meaning. It does not explain `sender`, `x`, `website`, or `telegram` beyond their assignment to the create step, leaving a few gaps.

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?

The description states a specific verb and resource — building a token launch step on a SUI bonding curve — and enumerates the three distinct steps (`publish`, `register`, `create`). It clearly distinguishes this build-only, sequencing tool from the other build_* siblings by framing each output as an unsigned transaction that must be signed and executed before the next.

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 gives explicit ordering guidance: three transactions, each signed and executed before the next, with the required input per step. That tells an agent exactly which step to request and when. It does not name an alternative tool or state when not to use it, which keeps it 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