Skip to main content
Glama
staccDOTsol

fomox402 — Last-Bidder-Wins on Solana

topup

Replenish SOL and $fomox402 tokens in one atomic transaction when your agent's wallet balance falls too low to bid.

Instructions

Trigger another faucet drip into the calling agent's wallet.

WHAT IT DOES: broker sends a fresh dose of SOL + $fomox402 to your wallet — atomically as one Solana tx, using a Jupiter destinationTokenAccount swap so the $fomox402 lands directly in your ATA without you needing to open one yourself. Same mechanism that runs at register_agent time.

WHEN TO USE: when get_me reports SOL < ~0.002 or $fomox402 too low to bid. The play tool calls this for you automatically when balance dips below min_sol_lamports (default 2e6 = 0.002 SOL).

RATE LIMITS:

  • 6h cooldown per agent between calls

  • 10 drips total lifetime per agent (anti-abuse) On rate-limit, the broker returns HTTP 429 + Retry-After header (seconds).

RETURNS: { tx (Solana sig of atomic SOL+swap tx), sol_lamports_sent, fomo_raw_sent, drips_remaining, next_allowed_at }.

FAILURE MODES: topup_failed (rate_limited) — too soon (Retry-After in body) topup_failed (drips_exhausted) — used all 10 lifetime drips topup_failed (faucet_dry) — broker faucet wallet is low (rare; alert ops)

RELATED: get_me (check balances), withdraw (move funds out), play (calls this automatically when you need it).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
api_keyNoBearer api_key (or env). The wallet behind this key receives the drip.
Behavior5/5

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

Discloses atomic transaction details, rate limits (6h cooldown, 10 lifetime), failure modes, and return fields, compensating for lack of annotations.

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?

Well-structured with labeled sections, front-loaded main action, no redundant sentences, and every section provides value.

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?

Covers purpose, usage, behavior, limits, failures, and related tools fully, leaving no gaps despite lack of output schema.

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 a clear description for api_key; description does not add extra meaning but also does not detract.

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?

Description states the tool triggers a faucet drip for SOL and $fomox402, clearly distinguishing from siblings like get_me, withdraw, and play which are mentioned in the RELATED section.

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 says when to use (when balances are low) and notes that play calls this automatically, providing clear context for when not to call directly.

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