Loading ToolBench
The Nano (XNO) toolkit for AI agents and developers. Send, receive, check balances, and manage payment requests without ever handling private keys.
xno-skills presents a domain-specific Nano cryptocurrency toolkit with 22 well-named tools covering wallet operations, transaction management, and cryptographic utilities. Tool naming is consistently strong (verb_noun pattern, action-oriented), descriptions are present and adequate for most tools, and input schemas are properly defined with JSON Schema types. However, output schemas are largely undocumented, the code shows tool implementations but the MCP tool registration does not include explicit return type documentation. Error handling guidance is minimal; several destructive/irreversible operations (nano_send, nano_submit_block, nano_receive) lack confirmation workflows or explicit recovery hints. Parameter descriptions are present but sometimes sparse (e.g., 'OWS wallet name' without explaining what OWS is or how to discover wallet names). The toolkit is functionally complete for its domain but falls short of production-grade documentation standards in output clarity and error recovery.
Get detailed account information for a Nano address
Build a state block hex from parameters
Change the representative (voting node) for a Nano account
Convert between Nano (XNO) and raw units
Decode a Nano address to its public key
Run diagnostics on the Nano RPC connection and PoW settings
Generate a QR code for a Nano address or payment request
Get the current balance and pending amount for a Nano wallet
Output schemas entirely undocumented, source code shows tool definitions but MCP tool registration lacks return type documentation. LLM cannot know what fields to expect or how to chain tools.
Destructive/irreversible operations (nano_send, nano_receive, nano_submit_block, nano_change_representative) lack dry-run, confirmation, or recovery guidance. Agents have no safety mechanism to prevent accidental fund loss.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | D | 57 | 2026-07-28+ | v2 |
Compute the hash of a state block hex
Get transaction history for a Nano account
List all Nano wallets available through OWS
Convert a public key to a Nano address
Receive pending blocks for a Nano wallet
Get account balance via RPC call
Probe RPC server capabilities
Get receivable (pending) blocks for an account
Send Nano to a destination address
Sign a message with a Nano wallet (without exposing the private key)
Submit a prepared state block to the Nano network
Validate a Nano address format
Verify a signed Nano message
Generate proof of work for a block hash
Parameter descriptions are sparse and domain-specific. Many assume LLM knowledge of Nano internals (e.g., 'representative', 'link field', 'proof of work', 'state block'). No beginner-friendly guidance on when to use each tool.
Error handling is absent. Tools marked IRREVERSIBLE or WRITE provide no guidance on failure modes, recovery, or what to do if the operation partially succeeds.
Implementation-specific naming exposes transport details. Tools like 'nano_rpc_account_balance' and 'nano_rpc_receivable' should hide RPC plumbing and expose user intent instead.
Overlapping tool functionality without clear guidance. Tools nano_get_balance and nano_rpc_account_balance appear to do the same thing; LLM may waste reasoning cycles deciding between them.
Parameter format constraints are missing. blockHex, hash, publicKey, signature parameters lack format documentation (hex case, length, encoding). LLM may pass invalid values.
Acronyms without explanation. 'OWS', 'RPC', 'PoW' appear in descriptions and parameter hints without definition. Non-experts cannot understand tool purpose.