o1-base-launcher
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| O1_API_KEY | Yes | A scoped o1 Launchpad API key from the o1 developer portal. Set this in your own operating system environment or a secret manager before starting the agent client; the server does not load .env automatically. | |
| BASE_RPC_URL | No | A Base RPC endpoint. Set this if you use another trusted Base RPC. | https://mainnet.base.org |
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": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| connect_base_walletA | Open the local wallet connection and approval page; connection is pending until the user connects a wallet. |
| get_connected_walletA | Return the current short-lived Base wallet session, if any. |
| get_wallet_balanceB | Read ETH or ERC-20 balance for the connected wallet. |
| get_o1_configC | Read live o1 Base launch configuration. |
| search_o1_tokensB | Search o1 Base tokens by name, symbol, or address. |
| get_o1_token_detailsC | Read a verified o1 token by Base address. |
| get_my_launchesB | List launches created by the connected wallet. |
| get_wallet_activityB | Read indexed o1 activity for the connected wallet. |
| prepare_token_launchB | Prepare a Standard Base o1 token launch. Requires a base64 image and a quote address from live config. |
| get_swap_quoteC | Get an exact-input o1 Base buy or sell quote. |
| prepare_buy_tokenC | Prepare a buy from a live quote ID. |
| prepare_sell_tokenB | Prepare a sell from a live quote ID. |
| prepare_eth_transferC | Prepare a direct ETH transfer in wei. |
| prepare_erc20_transferB | Prepare a direct ERC-20 transfer in human units; decimals are read on-chain. |
| prepare_creator_fee_claimC | Prepare a claim to the recorded recipient using a live o1 fee position. |
| request_wallet_approvalB | Place a previously prepared intent in the local page for explicit user and wallet approval. |
| get_transaction_statusC | Check on-chain receipt and optional o1 indexing for an intent or transaction hash. |
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 17 tools
Each tool targets a distinct resource or action: wallet session/balance/activity, token search/details, config, launches, and separate prepare_* intents for launch, buy, sell, ETH transfer, ERC-20 transfer, and fee claim. The prepare-then-request_wallet_approval two-phase pattern is explicitly described and does not blur boundaries.
Every tool follows a consistent snake_case verb_noun pattern (connect_*, get_*, search_*, prepare_*, request_*). No mixing of conventions or vague verbs.
17 tools is slightly heavy but justified by the breadth of the DeFi launch/swap/wallet domain, where each prepare_* maps to a distinct transaction type. Not bloated with redundant entries.
Covers the full lifecycle from wallet connection through quoting, preparing, approving, and checking transaction status, plus fee claims and activity. Minor gaps like canceling/discarding a prepared intent or a portfolio view are workaroundable.