Skip to main content
Glama

prepare_solana_nonce_close

Destructive

Close a durable-nonce account to reclaim its full SOL rent deposit, returning balance to the wallet. Subsequent sends require re-initialization.

Instructions

Tear down a previously-initialized durable-nonce account and return its full balance (~0.00144 SOL) to the main wallet. ix[0] = SystemProgram.nonceAdvance (self-protecting, same pattern as any durable-nonce-protected send — so this close tx itself won't expire during Ledger review), ix[1] = SystemProgram.nonceWithdraw (drains the balance). After broadcast, subsequent sends from this wallet will refuse until prepare_solana_nonce_init is run again. Refuses if no nonce account exists for the wallet.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
walletYesSolana wallet whose durable-nonce account should be closed. The full balance (~0.00144 SOL rent-exempt seed) is returned to this same wallet.
Behavior5/5

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

Exceeds annotations by detailing the two instructions (nonceAdvance and nonceWithdraw), the exact balance returned, and the refusal condition for subsequent sends.

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?

Four sentences, each adding essential context, but slightly verbose for a single-parameter tool. Still efficient and front-loaded.

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 preconditions, transaction structure, post-effects, and error case (refuses if no nonce). No gaps given no output schema.

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

Parameters5/5

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

Adds value beyond schema: specifies the exact SOL amount returned and confirms the balance goes to the same wallet, which is not in 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 the tool tears down a durable-nonce account and returns its balance, with specific verb and resource. It distinguishes from siblings like prepare_solana_nonce_init.

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?

Clear context: closes nonce account and warns about post-broadcast behavior, but no explicit when-not-to-use or alternatives mentioned.

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/szhygulin/recon-crypto-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server