Skip to main content
Glama
Sign In
Agentic AQUA

Agentic AQUA

Official
by AquaWallet
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

delete_wallet

Permanently removes a Bitcoin or Liquid wallet, its seed, and cached data through a two-step preview and explicit confirmation to prevent accidental deletion.

Instructions

Permanently delete a wallet, its seed and all its cached data (irreversible). Two-step: call WITHOUT confirm first to get a preview (balances, warning, confirm_token) and delete nothing; show it to the user, ask for explicit confirmation, then call again with confirm=true and that confirm_token. Use the 'delete_wallet' prompt for the safe workflow.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "wallet_name": "<wallet_name>"
    },
    "name": "delete_wallet"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmNoTwo-step flow: false/omitted returns a preview (balances, warning) and deletes nothing; true permanently deletes the wallet and its seed. Only set true after the user explicitly confirmed.
wallet_nameYesName of the wallet to delete
confirm_tokenNoSingle-use token from the preview; required with confirm=true.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.9/5.0
Behavior5/5

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

No annotations exist, so the description carries the full burden and does: it discloses that the first invocation deletes nothing and returns balances, a warning, and a token, and that the second invocation is permanent and destroys the seed and cached data. It also bounds the token to a single use, which prevents replay of a stale preview.

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?

Two sentences, front-loaded with the destructive scope before the procedural detail, and every clause (preview contents, token, user confirmation, prompt reference) carries actionable information with no filler.

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?

For a high-stakes irreversible mutation with no annotations and no output schema, the description covers what is destroyed, what the preview returns, how to confirm, and where the guided workflow lives. Nothing needed to invoke it safely is missing.

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 the baseline is 3; the description still adds workflow meaning by tying the confirm/confirm_token pair to a required human confirmation step rather than a bare boolean. Most individual field semantics, however, are already in the schema descriptions, so the added value is sequencing rather than new field-level detail.

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?

States a specific verb and resource plus exact scope: deletes the wallet, its seed, and all cached data, and flags it as irreversible. There is no competing delete tool among the siblings, so an agent can identify this unambiguously without opening the schema.

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?

Gives an explicit call sequence: first call without confirm to obtain a preview and token, show it to the user, obtain explicit confirmation, then re-call with confirm=true and the token. It also names a concrete alternative entry point ('delete_wallet' prompt) for the safe workflow.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools