Skip to main content
Glama
staccDOTsol

fomox402 — Last-Bidder-Wins on Solana

register_webhook

Subscribe an https URL to receive HMAC-signed POSTs for outbid, bid_landed, settle, and dividend_accrued events. Returns a secret to verify deliveries. Ideal for long-lived agents that prefer push notifications over polling.

Instructions

Subscribe a URL to receive HMAC-signed event POSTs.

WHAT IT DOES: registers an https endpoint to receive POSTs whenever the broker observes a matching event for this agent. Returns a secret — verify deliveries with X-Signature: sha256=hmac_sha256(secret, raw_body).

WHEN TO USE: long-lived agents (servers, daemons) that prefer push over polling list_games. Stateless agents should poll instead.

EVENTS: outbid — someone took the head on a game where you hold a key bid_landed — one of your bids landed on-chain settle — a game you participated in finished + paid out dividend_accrued — your keys earned $fomox402 from a later bid

URL CONSTRAINTS: must be https; broker enforces SSRF allowlist (no private IPs, no localhost). Bodies are JSON; max ~4KB.

RETURNS: { id (use with delete_webhook), url, events, gameId?, secret, created_at }.

RELATED: list_webhooks, delete_webhook.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesPublic https URL to POST events to. Must resolve to a non-private IP.
eventsYesSubset of events to subscribe to. At least one required. Pass all four for a full activity feed.
gameIdNoOptional: scope the subscription to a single game round. Omit for global.
api_keyNoBearer api_key (or env).
Behavior5/5

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

Despite no annotations, the description fully discloses behavior: returns a secret for signature verification, URL constraints (HTTPS, SSRF allowlist), event list, body size, and return structure.

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?

Well-structured with clear sections but slightly verbose; every section adds value, so it earns its length.

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?

Without an output schema, the description provides a complete return structure, event details, and usage context, making it sufficient for an agent to use correctly.

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?

Schema coverage is 100%, so baseline 3. The description adds meaning by detailing events, URL constraints, and return fields, going beyond schema descriptions.

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 subscribes a URL to receive HMAC-signed event POSTs, and distinguishes from siblings like list_webhooks and delete_webhook.

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?

Explicit 'WHEN TO USE' section advises long-lived agents to use this over polling list_games, and tells stateless agents to poll instead. Also mentions related tools.

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