Skip to main content
Glama

Launchpad curve plan

launchpad_curve_plan
Read-onlyIdempotent

Design a zero-creator-allocation fair launchpad tokenomics, bonding-curve depth, LP fee split, and immutable geometric Drip Vault schedule backed by on-chain ApexRevenueSplit parameters. Not advice. $0.003 per call over x402 (USDC on Arc, Base or Solana, or XNT on X1). Call once without payment for the terms, sign them with your own wallet, call again with payment.

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": {
      "symbol": "<symbol>"
    },
    "name": "launchpad_curve_plan"
  }
}

Input Schema

NameRequiredDescriptionDefault
chainNotarget chain: arc (default), base or x1
symbolYestoken ticker symbol (2 to 12 alphanumeric characters)
paymentNoa signed x402 payment (the base64 payload you would put in PAYMENT-SIGNATURE). Pass it and the purchase completes inside this tool call.
sybilGateNoanti-Sybil claim gate: eip712-passport (default), onchain-bond or zk-nullifier
poolFeeBpsNoAMM LP fee in bps (10 to 300, default 100 = 1%)
totalSupplyNototal fixed token supply (1000000 to 1000000000000, default 1000000000)
annualDecayPctNoannual geometric Drip Vault release rate in percent (1 to 90, default 18.25)
dripVaultSharePctNopercent of fixed supply locked in the immutable Drip Vault (20 to 80, default 50)
initialLiquidityUsdNoinitial paired USDC/XNT liquidity value in USD (100 to 100000000, default 10000)
projectedDailyVolumeUsdNoprojected 24h swap volume in USD for UBI fee simulation (default 25000)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true and openWorldHint=true, so the safety profile is covered. Beyond that, the description adds real behavioral facts: the call costs $0.003, supports USDC on Arc/Base/Solana or XNT on X1, requires a signed payment payload to complete, and that the vault schedule is immutable and backed by on-chain ApexRevenueSplit parameters. It also gives a 'Not advice' disclaimer. It does not say what the returned plan contains, keeping it below 5.

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?

The output artifact is front-loaded in the first sentence, followed by the constraints (not advice, cost, payment rails) and the two-step invocation protocol. Three sentences with no filler. The middle clauses are heavily noun-stacked, which slightly hurts first-pass comprehension.

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 read-only planning tool with 10 parameters and no output schema, the description covers purpose, cost, and the payment handshake well. What it omits is what the returned plan actually looks like and how the tuning parameters (dripVaultSharePct, annualDecayPct, poolFeeBps) trade off against each other. An agent can invoke it correctly but cannot predict or validate the result shape.

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% across all 10 parameters, so the schema already documents ranges and defaults for chain, poolFeeBps, totalSupply, and the rest. The description only adds meaning for the `payment` parameter, clarifying that it is the signed x402 payload normally sent as PAYMENT-SIGNATURE. Baseline 3 is correct when the schema carries the parameter burden.

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?

The description opens with a specific verb-and-resource pair ('Design a ... fair launchpad tokenomics, bonding-curve depth, LP fee split, and immutable geometric Drip Vault schedule') that tells an agent exactly what artifact it produces. It is dense with domain jargon (Drip Vault, ApexRevenueSplit) but unambiguous about the product. It does not name or differentiate itself from siblings such as launchpad or meal_curve, keeping it out of the top band.

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?

There is clear procedural guidance: 'Call once without `payment` for the terms, sign them with your own wallet, call again with `payment`,' which prevents the agent from guessing at the x402 handshake. However, there is no statement of when to prefer this tool over siblings like launchpad or meal_curve, and no exclusion conditions. Usage context is implied by 'fair launchpad' and 'zero-creator-allocation' rather than stated.

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