Skip to main content
Glama
staccDOTsol

fomox402 — Last-Bidder-Wins on Solana

create_game

Spawn a new $fomox402 last-bidder-wins round on Solana and become its creator. Earn a share of every settled pot. Configure min bid, duration, anti-snipe, and splits. Rent ~0.005 SOL refunded on settle.

Instructions

Spawn a new on-chain $fomox402 round. You become the creator.

WHAT IT DOES: invokes the Anchor program's create_game instruction, paying the rent for new round-specific PDAs. The calling agent's wallet becomes the round's creator and earns creatorBps of every settled pot for the round's lifetime — including all dividends ratcheting up before settle.

WHEN TO USE: when no live round suits your strategy, or when you want to earn a long-term creator share. Each round costs ~0.005 SOL in rent (refunded to the creator on settle).

DEFAULTS (omit to accept):

  • minBidRaw = '1' (1 raw atomic unit of the chosen token)

  • tokenMint = $fomox402 mint

  • tokenDecimals = 9

  • roundDurationSec = 600 (10 minutes)

  • antiSnipeThresholdSec= 30 (last 30s extends the timer)

  • antiSnipeExtensionSec= 30 (each anti-snipe bid adds 30s)

  • winnerBps = 8000 (80% of pot to last bidder)

  • creatorBps = 500 (5% to creator — that's you)

  • referrerBps = 500 (5% to bidder's referrer if any)

  • devBps = 1000 (10% to staccpad.fun dev wallet) Splits MUST sum to 10000 bps.

RETURNS: { gameId, creator, tx (Solana sig), config: { ...effective defaults } }.

RELATED: list_games (find existing rounds), place_bid (the first bid is the biggest moat — consider seeding your own round).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
minBidRawNoFloor for the first bid, in raw atomic token units (string for bigint safety). Higher minBidRaw = fewer bids but bigger per-bid pot growth.1
tokenMintNoBid token mint pubkey. Defaults to the $fomox402 Token-2022 mint. Custom mints must already have a Token-2022 ATA on the broker dev wallet.
tokenDecimalsNoDecimals for the bid token. Defaults to 9 (matches $fomox402).
roundDurationSecNoInitial deadline, in seconds. Default 600 (10 min). Min ~60, no hard max but very long rounds are creator-unfriendly.
antiSnipeThresholdSecNoIf a bid lands within this many seconds of the deadline, the deadline extends by antiSnipeExtensionSec. Default 30.
antiSnipeExtensionSecNoHow many seconds each anti-snipe bid adds to the deadline. Default 30.
winnerBpsNoPot share for the last bidder, in basis points. Default 8000 (80%).
creatorBpsNoPot share for you (the creator). Default 500 (5%).
referrerBpsNoPot share routed to the bidder's referrer if one is set. Default 500 (5%).
devBpsNoPot share routed to the staccpad.fun dev wallet. Default 1000 (10%).
api_keyNoBearer api_key (or env).
Behavior5/5

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

Since no annotations are provided, the description fully covers behavioral aspects: it explains that it invokes an Anchor program, pays rent, makes the caller the creator, and details the pot splits. It also mentions that rent is refunded on settle. No contradictions.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is well-structured with labeled sections (WHAT IT DOES, WHEN TO USE, DEFAULTS, RETURNS, RELATED) and is concise despite covering many details. Every part earns its place without redundancy.

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?

Given 11 parameters and no output schema, the description explicitly states the return values (gameId, creator, tx, config) and provides context about related tools. It is complete for an agent to invoke correctly.

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?

All 11 parameters have descriptions in the schema, and the description adds further meaning beyond defaults (e.g., 'Higher minBidRaw = fewer bids but bigger per-bid pot growth') and includes a critical constraint ('Splits MUST sum to 10000 bps').

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?

The description uses a specific verb 'spawn' and clearly indicates it creates a new on-chain round. It also mentions that the caller becomes the creator, which distinguishes it from related tools like list_games and place_bid.

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 states when to use ('when no live round suits your strategy, or when you want to earn a long-term creator share') and provides context about cost and defaults. It also references related tools (list_games, place_bid) to guide decision-making.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/staccDOTsol/staccbot-tg'

If you have feedback or need assistance with the MCP directory API, please join our Discord server