Skip to main content
Glama

OpenFinance — Easy Trading: Crypto, Stocks, Perps & Prediction Markets

openfinance-launchpad-v4

OpenFinance launchpad on Uniswap V4 (Robinhood Chain, EVM chain id 4663) — launch a token whose bonding curve IS a real Uniswap V4 position, trade it through the Universal Router, and graduate it into locked full-range liquidity.

WHICH LAUNCH TOOL TO USE ON ROBINHOOD CHAIN. There are three, and they are different venues — not alternative spellings of one: • openfinance-launchpad-v4 (this tool) — Uniswap V4 pools, paired against an APPROVED QUOTE TOKEN (e.g. USDG), with a snipe tax and a creator tax. Use when the user names Uniswap/V4, names a quote asset such as USDG, or wants the token tradable through the Uniswap router. • openfinance-launchpad-wrapper — the Pons curve plus a permanent FEE MODULE (burn / split / raffle / holders). Use when the ask is about where the fees go. • openfinance-pons-launch — legacy Pons reads only. If the user just says "launch a token on Robinhood Chain" with nothing about fee modules or Uniswap, ASK which venue rather than guessing: the choice is permanent and the pools are not interchangeable. For SOLANA launches use openfinance-launchpad (Meteora DBC) — a different chain entirely.

HOW A LAUNCH WORKS HERE

  1. launch deploys the token and opens a V4 pool against pairToken (an approved quote asset — call list_quote_assets first; passing anything else is rejected on chain).

  2. The curve is a V4 position, so the token is tradable through the Universal Router immediately. buy / sell go through get_quote → router.

  3. When the curve fills, the launch graduates: reserves become locked full-range liquidity. buy may graduate as a side effect when the buy consumes the rest of the curve — the response says side: 'graduate' when that happened.

AMOUNTS ARE BASE UNITS. amount on buy/sell/quote is a raw integer string in the token's smallest unit, never a decimal. The pair asset's decimals are NOT always 18 — USDG is 6, so 1 USDG is "1000000". Read decimals from list_quote_assets and convert; a 10^12 error here spends a million times the intended amount.

TAXES, AND WHY A QUOTE IS CALLER-SPECIFIC • A snipe tax of 99% applies for the first 3 seconds after launch, decaying to 0. It depends on WHO is swapping, so get_quote simulates from the trader's own address. A quote taken for someone else misprices that window and the swap then fails its minimum output. • A creator tax (0-10%, creatorTaxBps) is fixed at launch and cannot be changed afterwards. • The hook takes 1% of each swap; 30% of that is the protocol's share.

DEV BUY. devBuy is an amount of the PAIR token (a decimal string here, e.g. "1" for 1 USDG — the server converts using that asset's decimals) bought for the creator in the same transaction. It needs that balance in the user's server wallet; the server sends the ERC20 approval itself.

IRREVERSIBLE. A launch deploys a contract and opens a real pool with real liquidity. Name, symbol, pair token, and creator tax are frozen at launch. Confirm the parameters with the user before calling launch, and never launch to "test" the tool.

ACTIONS: Reads (no key needed): get_readiness, list_quote_assets, get_pair_terms, list_launches, get_pool, get_market, get_candles Reads (key): get_quote, get_fees Writes (key, real money): launch, buy, sell, graduate, claim_fees

Prerequisite: openfin-setup — the user needs a server-authorized Privy EVM wallet (POST /agent/auth/authorize-server), funded with the pair token for a buy or a dev buy.

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": {
      "action": "<action>"
    },
    "name": "openfinance-launchpad-v4"
  }
}

Input Schema

NameRequiredDescriptionDefault
tfNoCandle timeframe (get_candles, get_market). Default 1h.
logoNoAn already-hosted logo URL, instead of `image` (launch).
nameNoToken name (launch).
sideNoQuote direction (get_quote). Default buy.
imageNoBase64 or data-URL artwork, pinned to IPFS server-side (launch).
limitNoPage size (list_launches). Default 50.
tokenNoA launched token address (buy, sell, graduate, get_quote, get_pool, get_market, get_candles).
actionYesWhich launchpad operation to run.
amountNoBASE UNITS as an integer string. buy: pair-token in. sell: tokens in. Never a decimal.
devBuyNoPair-token amount to buy for the creator in the launch tx, as a DECIMAL string (e.g. "1" = 1 USDG).
offsetNoPage offset (list_launches). Default 0.
symbolNoToken symbol (launch).
traderNoAddress to simulate the quote from (get_quote); defaults to the caller.
creatorNoFilter launches by creator address (list_launches).
discordNoDiscord URL (launch).
includeNoComma list for get_market: candles,trades,holders. Default all three.
twitterNoTwitter/X URL (launch).
websiteNoWebsite URL (launch).
currencyNoFee currency to read or claim (get_fees, claim_fees).
telegramNoTelegram URL (launch).
farcasterNoFarcaster URL (launch).
pairTokenNoThe approved quote token to pair against, as an ADDRESS (launch, get_pair_terms). Must come from list_quote_assets.
recipientNoFee recipient address; defaults to the creator (launch).
descriptionNoToken description (launch).
slippageBpsNoSlippage tolerance in bps (buy, sell). Default is the server’s.
minDevTokensNoMinimum tokens the dev buy must return, base units (launch, slippage guard).
creatorTaxBpsNoCreator tax in basis points, 0-1000 (0-10%). FROZEN at launch — cannot be changed later. Default 0.
snipeTaxExemptionsNoAddresses exempt from the 3-second snipe tax (launch).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

With no annotations, the description carries the full burden and does so: it discloses the 99% snipe tax decaying over 3 seconds, the frozen 0-10% creator tax, the 1% hook fee, graduation semantics (including buy causing a side-effect graduation), the irreversibility of name/symbol/pair/tax, and the server-side ERC20 approval for devBuy. It also explains why quotes are caller-specific, which is a non-obvious failure mode.

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?

Long, but justified for a 14-action multiplexed tool and well front-loaded with bold section headers and bullets. A few passages (the 'how a launch works' sequence) partly restate the action list, so it is not maximally tight, but every section carries decision-relevant information.

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?

Covers the irreversible write path, tax model, amount encoding, prerequisites and the venue decision thoroughly, and with no output schema it reasonably omits return shapes while still noting the graduation response marker. The read-only actions (get_readiness, get_fees, claim_fees, list_launches pagination) are named but not explained, leaving minor gaps.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so baseline is 3, but the description adds real meaning beyond the schema: the base-units rule with the concrete USDG 6-decimal example and the 10^12 warning, the deliberate contrast between decimal-string devBuy and integer-string amount, pairToken must come from list_quote_assets or it is rejected on chain, and trader defaulting to the caller because the quote depends on who swaps.

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+resource up front: launching a token whose bonding curve is a real Uniswap V4 position on Robinhood Chain, with buy/sell/graduate/claim_fees actions enumerated. It explicitly distinguishes itself from the two sibling launch tools (wrapper, pons) and from the Solana launchpad, so an agent can route without opening any schema.

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?

Gives explicit inclusion criteria per venue ('use when the user names Uniswap/V4, a quote asset such as USDG') and a when-not rule ('if the user just says launch a token... ASK which venue rather than guessing'). It also lists reads vs writes, flags which actions need a key or move real money, and names the openfin-setup prerequisite.

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.