Skip to main content
Glama
arcnow-io

@arcnow/mcp

Official
by arcnow-io

Quote a launch

arcnow_quote_launch
Read-onlyIdempotent

Get the exact launch cost before spending: launch fee, initial buy, 1% trade fee, tokens received, and predicted token addresses. Confirms the irreversible total upfront.

Instructions

What launching a token would cost, before anything is spent: the launch fee the quote registry sets for the quote (zero on arcnow.io's networks — launching is free — but read live, never assumed), the initial buy, the 1% trade fee the initial buy itself pays, the tokens the creator would receive, and — given a creator address — the exact addresses the token and its curve would land at.

Costs nothing and signs nothing. Always call this before arcnow_launch and show the user the total, because a launch is irreversible: the name, symbol, supply, curve shape and graduation venue are fixed at that transaction and can never be changed afterwards, by anyone, including whoever launched it.

THE QUOTE. A token is priced for life in the quote it launches in: quote names it by symbol or address — native USDC by default, or an ERC-20 such as EURC that the quote registry accepts (arcnow_quote_tokens). The initial buy — and any launch fee — is in that quote, and so is every trade in the token afterwards. Native USDC is paid as msg.value; an ERC-20 is pulled by the launchpad after an exact approval.

The total is EXACTLY what a launch requires, not a minimum — for native USDC the launchpad reverts on an overpayment as readily as an underpayment, because it has no refund path.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesThe token's name. Permanent — there is no setter for it, on any contract, ever.
quoteNoOptional: the quote token to launch in, by symbol ("USDC", "EURC") or by address. Defaults to native USDC. The token is priced in it FOR LIFE: its initial buy and every trade in it afterwards. A symbol is looked up in this network's own quote tokens only. arcnow_quote_tokens lists them with whether the quote registry accepts each and this server's spend cap for it; a quote with no cap cannot be launched in here.
symbolYesThe token's ticker. Permanent, and not unique: two tokens may share a symbol, so an address is the only identifier that means anything.
creatorNoOptional: the address that would launch. Given one, this also predicts the token and curve addresses — valid only for that address's CURRENT launch nonce and exactly these parameters.
migratorNoOptional: where this token graduates to, snapshotted into the curve at launch and immutable thereafter. Defaults to the platform's default migrator.
platformNoOptional: the PlatformConfig to launch under. Defaults to arcnow.io's own, which is what almost every launch uses.
initialBuyYesHow much of the launch's quote the creator spends buying their own token in the launch transaction, in whole units, with no more decimals than the quote has. It is an ORDINARY buy: it runs through the curve and pays the 1% trade fee. There is no fee-free entry into a curve, and no launch fee on top of it on arcnow.io's networks. "0" is allowed.
metadataUriYesREQUIRED. An ipfs:// or https:// URI for the token's metadata — image, description, links. The launchpad reverts a launch whose URI is empty (InvalidLaunchParameters), so there is no launching without one. Permanent: it is stamped into the token at launch and there is no setter.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.2.0
    • changedInput schema / properties / initialBuy / description
      Previous value: -"How much of the launch's quote the creator spends buying their own token in the launch transaction, in whole units, with no more decimals than the quote has. It is an ORDINARY buy: it runs through the curve and pays the 1% trade fee on top of the flat launch fee. There is no fee-free entry into a curve. \"0\" is allowed."New value: +"How much of the launch's quote the creator spends buying their own token in the launch transaction, in whole units, with no more decimals than the quote has. It is an ORDINARY buy: it runs through the curve and pays the 1% trade fee. There is no fee-free entry into a curve, and no launch fee on top of it on arcnow.io's networks. \"0\" is allowed."
    • changedInput schema / properties / quote / description
      Previous value: -"Optional: the quote token to launch in, by symbol (\"USDC\", \"EURC\") or by address. Defaults to native USDC. The token is priced in it FOR LIFE: its launch fee, its initial buy, and every trade in it afterwards. A symbol is looked up in this network's own quote tokens only. arcnow_quote_tokens lists them with whether the quote registry accepts each and this server's spend cap for it; a quote with no cap cannot be launched in here."New value: +"Optional: the quote token to launch in, by symbol (\"USDC\", \"EURC\") or by address. Defaults to native USDC. The token is priced in it FOR LIFE: its initial buy and every trade in it afterwards. A symbol is looked up in this network's own quote tokens only. arcnow_quote_tokens lists them with whether the quote registry accepts each and this server's spend cap for it; a quote with no cap cannot be launched in here."
  2. First observedv0.1.1

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent; description adds that it costs nothing and signs nothing, reads live fee (never assumed), and that total is exact with revert on overpayment. No contradiction; adds substantial behavioral context.

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?

Well-structured with clear sections (purpose, usage, quote semantics, exactness). Each sentence adds substantive info, but it's slightly longer than necessary; still front-loaded and no filler.

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

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema, so description lists output components (fee, initial buy, trade fee, tokens, addresses) and explains irreversibility and payment exactness. Complete for an agent to call correctly.

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 covers all 8 params with detailed descriptions (100% coverage), so baseline is 3. The description adds conceptual context (quote concept, payment methods, exactness) but doesn't restate per-param details; it enhances understanding of parameter roles beyond schema.

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?

Clearly states the tool's purpose: it returns the exact cost of launching a token (launch fee, initial buy, trade fee, tokens received, and predicted addresses). It differentiates itself from sibling quote tools (arcnow_quote_buy/sell) by focusing on launch and names arcnow_launch as the execution counterpart.

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?

Explicitly instructs to call this before arcnow_launch and show the user the total, with a strong rationale (irreversibility). Also references arcnow_quote_tokens for quote token selection, giving clear when-to-use and alternatives.

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