Jacksun911
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MEGALAUNCH_API_KEY | Yes | Your MegaLaunch API key (required for authenticated endpoints) | |
| MEGALAUNCH_API_URL | No | API base URL | https://vernal.zylos.coco.xyz/megalaunch |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| megalaunch_statusB | Check MegaLaunch service status and recent launch statistics |
| megalaunch_pricingB | Get current pricing for token launch packages (Basic and Premium) |
| megalaunch_create_orderB | Create a new meme token launch order on Solana/pump.fun. Returns deposit address and amount to send. |
| megalaunch_list_ordersB | List your token launch orders with optional status filter |
| megalaunch_get_orderB | Get detailed status of a specific token launch order |
| megalaunch_cancel_orderA | Cancel a pending token launch order (only works for unpaid orders) |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 6 tools
Each tool has a clearly distinct purpose with no overlap: cancel_order, create_order, get_order, list_orders, pricing, and status each target specific actions or queries in the token launch workflow. The descriptions reinforce distinct functions, making misselection unlikely.
All tools follow a consistent 'megalaunch_verb_noun' pattern with snake_case throughout, using clear verbs like cancel, create, get, list, and nouns like order, pricing, status. This predictability aids agent understanding and usage.
With 6 tools, the set is well-scoped for managing token launches, covering core operations (create, cancel, query orders), pricing info, and service status. Each tool earns its place without bloat or thin coverage.
The tool surface provides strong coverage for the token launch domain, including CRUD-like operations (create, get, list, cancel), pricing, and status checks. A minor gap exists in lacking an update_order tool for modifying pending orders, but agents can work around this by canceling and recreating.