Skip to main content
Glama
staccDOTsol

fomox402 — Last-Bidder-Wins on Solana

burn_key

Burn one of your keys on a Solana round to increase the per-key dividend rate for your remaining keys and reduce competitors' share. Use when you hold many keys and the pot is still growing.

Instructions

Burn ONE key on a round to permanently boost your share on the remaining keys.

WHAT IT DOES: invokes the Anchor program's burn_key_token instruction. The burnt key's stake is folded into the round's divPerKeyScaled, increasing the per-key dividend rate for every remaining keyholder. Your remaining keys benefit proportionally to your share of post-burn keys.

WHEN TO USE: only when you hold many keys (>5) on a round whose pot is still ratcheting up. The math: if your_keys / total_keys is large, burning ONE key transfers a big chunk of your-vs-other dividend power — but you keep the rest of your keys. if your_keys / total_keys is small, the burn mostly subsidises others.

IRREVERSIBLE: burnt keys are gone. The on-chain account is closed and the rent is reclaimed; you cannot re-mint a key without placing a new bid.

RETURNS: { tx (Solana sig), gameId, keysBefore, keysAfter (= keysBefore - 1), newDivPerKeyScaled (the boosted rate) }.

FAILURE MODES: burn_key_failed (no_keys) — you don't hold any keys on this round burn_key_failed (round_settled) — round is already gameOver

ADVANCED USE — counter-burn defence: if a competitor is dominating divs by holding many keys, burning your own can flip the per-key rate higher than their additional bid cost, pricing them out.

RELATED: claim_dividend (collect what your keys earned), place_bid (mints a fresh key — opposite of this).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
gameIdYesRound you hold keys on and want to burn one of.
api_keyNoBearer api_key (or env). Must be the wallet that holds the keys.
Behavior5/5

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

With no annotations, the description fully discloses behavior: explains irreversibility, account closure, rent reclaim, failure modes, and return values. Even includes advanced counter-burn defense strategy.

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 clear sections, bullet points, and front-loaded main action. Every sentence is informative; no wasted words despite 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?

Given no output schema, the description covers return values, failure modes, irreversible nature, and advanced use. Provides a complete picture for an agent to use confidently.

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% with descriptions; description adds context by specifying that api_key must be from the wallet holding keys and that gameId is the round with held keys. Adds value beyond schema but not extensively.

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's purpose: burning one key to permanently boost share on remaining keys, explicitly mentioning the Anchor instruction and effect on dividend rate. It distinguishes from siblings like claim_dividend 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?

Provides explicit 'WHEN TO USE' section with mathematical reasoning and recommends use only when holding many keys. Lists failure modes and related tools, offering clear guidance on when not to use and alternatives.

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