Solobank MCP has 14 tools with basic schemas and descriptions, but significant gaps limit production readiness. All tools have descriptions (10-200 chars, mostly adequate), and input schemas are present with type definitions. However, parameter descriptions are sparse or missing context. Many tools lack output schema documentation. Error handling is minimal, no recovery guidance, no categorization of retryable vs. fatal errors. The server exposes financial operations (swap, lend, borrow, send) without documented safeguards, confirmation patterns, or dry-run validation. Tool naming is verb-noun compliant but descriptions do not explain WHEN to use each tool or dependencies between them (e.g., solobank_swap vs solobank_swap_quote). No tool annotations (readOnlyHint, destructiveHint) despite clear risk levels. Parameter constraints are underdocumented (e.g., slippageBps has no range; protocol enum values not validated).

• Add output schema documentation to all tools. Example: solobank_swap should document {txSignature: string, fromAmount: number, toAmount: number, executedPrice: number}. This enables LLMs to chain tools and extract results.
• Add dryRun parameter to solobank_swap, solobank_lend, solobank_borrow, solobank_repay, solobank_rebalance. Let agents preview transactions before execution. Pair with clear descriptions: 'If dryRun=true, return estimated outcome without broadcasting.'
• Add enum constraints to schema for protocol parameter. Change {type: string} to {type: string, enum: [kamino, marginfi, auto]}. Add min/max to slippageBps (e.g., 0-10000 basis points).
• Implement tool annotations in MCP schema. Mark solobank_address, solobank_balance, solobank_services, solobank_swap_quote, solobank_lending_rates with readOnlyHint=true. Mark solobank_send, solobank_swap, solobank_lend, solobank_borrow, solobank_repay, solobank_withdraw, solobank_rebalance with destructiveHint=true.
• Add error handling with recovery guidance. Example: 'Insufficient balance. Current balance: {balance}. Try solobank_balance() to check available funds.' Categorize errors: retryable (network timeout), user-fixable (insufficient balance), fatal (invalid address).