Skip to main content
Glama
staccDOTsol

fomox402 — Last-Bidder-Wins on Solana

play

One-shot autonomous bidding: checks balances, topups SOL, picks the highest-pot live game, and bids via x402 unless you are already holding the head position. Returns a structured status for recurring agent loops.

Instructions

One-shot autonomous playbook. The ONLY tool a stateless agent loop needs.

WHAT IT DOES: collapses the typical play cycle into a single call:

  1. get_me to check SOL/$fomox402 balances.

  2. If SOL < min_sol_lamports, call topup (silently swallowing rate-limits).

  3. list_games, filter to live rounds (gameOver=false, deadline > now+10s), sort by tokenPot desc, pick highest.

  4. If you're already the head bidder AND deadline > sit_if_head_threshold_sec in the future → don't bid, return status='sit_holding_head'.

  5. Else place_bid at effective_min + 1 raw via the full x402 flow.

Returns one structured status object with everything that happened, so prompt-style agents can run on a 30–60s cron without holding any state.

WHEN TO USE: as the only tool in a recurring agent loop. Drop into Claude Desktop / Cursor / Goose / a cron job and run forever. Equivalent to the autonomous-mode flow described in the server-level instructions.

POSSIBLE STATUSES (in returned JSON): 'no_live_games' — nothing biddable; just wait and try again 'sit_holding_head' — you're winning, no action needed 'bid_landed' — bid placed (x402_paid true/false depending on flow)

And error statuses if any sub-step fails: play_get_me_failed, play_list_games_failed, play_x402_pay_failed, play_bid_first_leg_failed, play_bid_second_leg_failed, play_402_no_nonce.

RETURNS: { status, gameId?, amountRaw?, x402_paid?, x402_fee_tx?, tx?, topup? (sub-result of any topup attempt), timer_remaining_sec?, note? }.

RELATED: get_me, list_games, place_bid, topup, claim_winnings — call those individually if you want fine-grained control.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
min_sol_lamportsNoTrigger a topup attempt when SOL balance falls below this many lamports. Default 2_000_000 (= 0.002 SOL). Set to 0 to disable auto-topup entirely.
sit_if_head_threshold_secNoIf you're already the head bidder and the round's deadline is more than this many seconds away, the tool returns 'sit_holding_head' instead of bidding (saves fees). Default 60. Set to 0 to always bid even when winning.
api_keyNoBearer api_key (or env).
Behavior5/5

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

No annotations provided, but the description fully details the step-by-step behavior including balance checks, auto-topup, filtering games, bidding logic, error handling, and rate-limit swallowing, providing all necessary 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?

The description is well-structured with bold headers and front-loaded purpose, but is somewhat long. Every section adds value, though minor trimming could improve conciseness.

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 no output schema, the description completely explains the return format, possible statuses, and error cases. It also relates to sibling tools, making it fully complete for an agent to decide to use this tool.

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 coverage is 100% with clear parameter descriptions. The tool description references parameters in context but does not add significant new semantics beyond what the schema provides, meeting the baseline of 3.

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 clearly states the tool is a 'One-shot autonomous playbook' that collapses multiple steps into a single call, providing a specific verb+resource ('play') and distinguishing it from siblings by mentioning they are for fine-grained control.

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?

The 'WHEN TO USE' section explicitly says it is for recurring agent loops, and 'RELATED' lists alternatives for fine-grained control, giving clear guidance on when to use this tool vs. siblings.

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