Skip to main content
Glama
Sign In
Agentic AQUA

Agentic AQUA

Official
by AquaWallet
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

lw_import_descriptor

Import a watch-only Bitcoin or Liquid wallet from a CT descriptor by providing a wallet name and network, enabling balance and address monitoring without private keys.

Instructions

Import a watch-only wallet from a CT descriptor

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": {
      "descriptor": "<descriptor>",
      "wallet_name": "<wallet_name>"
    },
    "name": "lw_import_descriptor"
  }
}

Input Schema

NameRequiredDescriptionDefault
networkNoNetwork to usemainnet
descriptorYesCT descriptor string
wallet_nameYesName for the wallet

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior2/5

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

No annotations provided. Description does not disclose side effects (e.g., wallet creation, overwrite behavior), permission requirements, or reversibility. For a mutation tool, this is insufficient.

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?

Single sentence with no wasted words. Appropriate length, though slightly terse. No unnecessary information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Medium complexity tool (3 params, enum) with no output schema or annotations. Description lacks guidance on return values, error conditions, or prerequisites (e.g., needing a descriptor from export).

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

Parameters3/5

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

Schema coverage is 100% with descriptions for all 3 parameters. The description adds no additional meaning beyond schema. Baseline 3 is appropriate.

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?

Description clearly states the action (import), resource (watch-only wallet), and source (CT descriptor). It distinguishes from siblings like btc_import_descriptor (Bitcoin) and lw_import_mnemonic (mnemonic-based).

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

Usage Guidelines3/5

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

No explicit guidance on when to use versus alternatives like btc_import_descriptor or lw_import_mnemonic. The implied context is via tool name prefix 'lw_' but description does not help agent decide.

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