Skip to main content
Glama
Sign In

EventTrader MCP

by com.cymetica
OverviewDiscussionsAdmin

Launchpad Launch Token

launchpad_launch_token
Destructive

Launch a token on Robinhood Chain for $0: returns the exact unsigned createToken transaction (to/value/data) for YOUR wallet to sign and broadcast. Non-custodial — no key ever leaves you. Creators earn 80% of every 0.25% trade fee, forever. On Circle's Arc (chain_id 5042, testnet 5042002) there is NO platform fee: 0% trade fee and 100% of LP fees to the creator.

Input Schema

NameRequiredDescriptionDefault
nameYesToken name (1-64 chars)
symbolYesTicker (1-16 chars)
dev_buyNoOptional atomic dev-buy (0-10) in the chain's native currency (ETH on Robinhood Chain, USDC on Arc), sent as tx value
discordNoDiscord invite URL (immutable social link)
partnerNoOptional whitelabel partner slug to attribute this launch to (e.g. 'coinpedia' when launching from a Coinpedia surface). Same factory/curve/token — only the partner rev-share attribution differs. Requires launch_wallet. Fail-soft: an unknown/disabled partner is reported in the response's `attribution` but never blocks the launch
twitterNoX/Twitter URL (immutable social link)
websiteNoProject website URL (immutable social link)
chain_idNoLaunchpad chain (default: first enabled, 4663 Robinhood Chain; 5042 = Arc, where value_wei is native USDC)
telegramNoTelegram URL (immutable social link)
image_urlNoLogo/image URL (immutable)
platformsNoArc only: ALSO launch this same token on other Arc launcher platforms (slugs from launchpad_list_launchers, e.g. ['arcpad','lift','warp']). Each comes back in `cross_launches`: a factory platform (ArcPad, lift.fun, Radian) as an unsigned launch tx against THAT platform's factory whose value_wei is its own launch fee, paid by you to them (ArcPad: none); a site platform (Warp, Arcodian, Flipt, ubi, Minara, ARCLaunch, Archemist, Long.supply, act.fun) as `create_url` + `fields` — open the page with your browser tool, enter exactly those fields, sign with your wallet. EventTrader adds nothing. Afterwards call launchpad_record_cross_launch (tx_hash for a factory launch; token_address + symbol for a site launch)
descriptionNoToken description (immutable)
dev_buy_ethNoLegacy alias of dev_buy (same unit: ETH on Robinhood Chain, USDC on Arc)
launch_walletNoThe 0x address you will SIGN this launch with. Required only when `partner` is set, so the indexer can attribute the launch to the partner (it matches this against LaunchCreated.creator within 48h)
creator_walletNoWallet that receives creator fees (default: the signing wallet). Immutable
creator_tax_bpsNoOptional EXTRA creator fee on curve trades in bps (100 = 1%; 0 up to the live factory cap, read max_creator_tax_bps from GET /api/v1/launchpad/onchain/config), 100% to the creator side, locked forever
share_fees_with_holdersNoRoute ALL creator-side fees to holders who stake (irreversible; the creator wallet never receives fees). Default false here and in the web launcher — pass true only to opt in

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / share_fees_with_holders / description
      Previous value: -"Route ALL creator-side fees to holders who stake (irreversible; the creator wallet never receives fees). Default false here; the web launcher defaults to true — pass it explicitly"New value: +"Route ALL creator-side fees to holders who stake (irreversible; the creator wallet never receives fees). Default false here and in the web launcher — pass true only to opt in"
  2. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and non-idempotent, and the description adds genuinely new behavioral context: non-custodial signing, no key ever leaves the caller, the returned payload shape, and the fee/rev-share economics (80% of 0.25%, Arc's 0% platform fee). It stops short of flagging the launch itself as irreversible or noting what happens to dev_buy funds on failure.

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?

Front-loaded with the core action and return artifact, then economics. The fee/tax sentences are useful but slightly tangential; overall tight with no filler.

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 17-parameter destructive tool with no output schema, the description explains the return payload and safety model, which is the key gap it must fill. Cross-launch and irreversibility details live mostly in schema field descriptions, but the description surfaces the workflow adequately.

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%, so the schema already carries parameter meaning and the baseline of 3 applies. The description only reinforces chain context (Robinhood Chain vs Arc) and fees, adding little detail the schema does not already provide.

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 verb and resource ('Launch a token on Robinhood Chain') plus the exact artifact returned ('the exact unsigned createToken transaction (to/value/data)'). An agent can distinguish this from siblings like launchpad_trade_quote or sui_launchpad_prepare without opening the schema.

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?

Clearly frames the usage context: non-custodial, wallet signs and broadcasts, and names the follow-up step (launchpad_record_cross_launch for cross-launches). However, it gives no explicit when-not guidance or direct comparison to related launchpad siblings, leaving some routing inference to the agent.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All EventTrader MCP toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources