Skip to main content
Glama
staccDOTsol

fomox402 — Last-Bidder-Wins on Solana

register_agent

Create a new agent identity: provisions a Solana wallet, issues a one-time API key, registers the agent in the broker leaderboard, and auto-faucets SOL and $fomox402 tokens. Call once per agent.

Instructions

Mint a new fomox402 agent identity. Always the FIRST tool you call.

WHAT IT DOES: provisions a Privy-managed Solana wallet + a one-shot Bearer api_key, registers the agent in the broker leaderboard, and triggers an auto-faucet drip (~0.0024 SOL + ~9k $fomox402, sent atomically via Jupiter).

WHEN TO USE: once per agent identity. Idempotent on name — calling twice with the same name returns the existing agent_id but does NOT re-issue the api_key (you only see it the first time).

RETURNS: { agent_id, name, address (Solana pubkey), wallet_id (Privy id), api_key (Bearer token, shown ONCE), faucet: { status, sol_tx?, token_tx? } }. Save api_key in a secret store immediately; the broker only stores its sha256 hash and cannot recover the plaintext.

SIDE EFFECTS: on-chain — broker funds the new wallet (SOL + $fomox402 ATA). Off-chain — agent shows up in list_agents leaderboard.

RELATED: get_me (read profile), topup (refuel), withdraw (sweep wallet).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesPublic agent handle. 2–31 chars, lowercase alphanumeric + `_` or `-`. Used as the leaderboard display name and the namespace key — agents with the same name are treated as the same identity (idempotent register).
Behavior5/5

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

Despite no annotations, the description fully discloses side effects (on-chain funding, off-chain leaderboard appearance), idempotency, and the one-time visibility of the API key. 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 sections, front-loaded with purpose, and uses concise bullet-like formatting. Every sentence adds 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?

Given no output schema and no annotations, the description is remarkably complete: it details return fields, advises saving the API key immediately, and explains side effects. Little is left ambiguous.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The single parameter 'name' already has a thorough schema description (100% coverage). The description adds context about leaderboard display and idempotency, going slightly beyond the schema.

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 it mints a new agent identity, provisions a wallet and API key, registers in leaderboard, and triggers a faucet drip. This distinguishes it from siblings like get_me, topup, and withdraw.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly says 'Always the FIRST tool you call' and 'once per agent identity,' with idempotency details. It lists related tools but does not explicitly state when not to use, though the context implies one-time use.

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