nano-wallet
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| NANO_NODE_URL | No | URL of the Nano node used for balance and receive operations. | |
| NANO_WALLET_ALLOW_SEND | No | Set to '1' to enable the send tool; otherwise send is disabled. | |
| NANO_WALLET_MAX_SEND_XNO | No | Maximum amount in XNO that can be sent per call (default 1.0 XNO). | |
| NANO_WALLET_REPRESENTATIVE | No | Override the representative account for new wallets. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| create_addressB | Generate a Nano (XNO) receiving address inside this process. Offline: no network call is made. The seed and private key are never returned, transmitted, logged or displayed. |
| validate_addressA | Checksum-verify a Nano (XNO) address. Returns valid=false with a machine-readable reason instead of throwing. A Nano address that fails its checksum looks entirely normal to the eye and can never receive a payment. |
| balanceB | Read an account's confirmed balance and what is waiting to be pocketed. |
| receiveB | Pocket incoming XNO. Receiving is not spending: it moves nothing out of the account and passes through no spend gate. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
Each tool targets a clearly distinct action and resource: address creation, address validation, balance query, and receiving funds. There is no overlap in purpose, so an agent can easily select the right tool.
Tool names mix conventions: create_address and validate_address use verb_noun, while balance is a bare noun and receive is a bare verb. The names remain readable, but the pattern is not fully consistent.
Four tools is a tight, reasonable set for a receive-focused Nano wallet, and each tool appears to earn its place. It is slightly thin for a full wallet, but appropriate if the scope is deliberately limited.
The set covers address creation/validation, balance checks, and receiving funds, but omits sending/spending, transaction history, and broader account management. For a server named nano-wallet, the lack of send capability is a notable gap.