pay-mcp has clear, actionable tool names (pay_balance, pay_send, pay_request, pay_history) that follow verb_noun conventions. All four tools have descriptions (103-128 chars, within 10-1024 range) and explicit input schemas with typed properties. However, parameter descriptions are sparse and sometimes generic. Output schemas are not documented anywhere, responses are text blobs without structure. Error handling exists (success/error fields in send result) but lacks recovery guidance. The server follows a simple MCP pattern but misses several production-grade touches: no input validation examples, no pagination docs despite history accepting a limit param, and no security considerations around wallet addresses or transaction amounts. STDIO transport is a hard constraint that caps protocol readiness.

• Document output schemas for all tools. E.g., pay_balance should return {address: string, balance: string, network: string, is_own_wallet: boolean}. pay_send should return {success: boolean, tx_hash?: string, explorer_url?: string, error_code?: string, error_message?: string}.
• Add a confirmation step to pay_send: require a separate confirm_payment(tx_id) call before funds leave the wallet. Or implement dry-run mode that returns 'would send X USDC to address Y' and requires explicit approval.
• Specify amount parameter format precisely. Replace 'Amount in USDC (e.g., "10.50")' with 'Amount in USDC as a decimal string, up to 6 decimal places (e.g., "10.50", "100.123456"). Max 1,000,000 USDC per transaction.'
• Add address validation and recovery guidance: 'Recipient address as 0x-prefixed Ethereum address (42 chars total, e.g., 0x742d35Cc6634C0532925a3b844Bc9e7595f42aE0). Invalid format example: 0x742d35Cc6634C0532925a3b844Bc9e7595f (too short) → error: Invalid address format.'
• Enhance error responses in pay_send with error codes and recovery hints: {success: false, error_code: 'INSUFFICIENT_BALANCE', error_message: 'Your balance (5.00 USDC) is less than the requested amount (10.00 USDC). Check your balance with pay_balance and try a smaller amount.'} vs current 'Error: ...'
• For pay_history, implement proper pagination: return {transactions: [...], total_count: 542, limit: 20, offset: 0, has_more: true}. Allow offset/cursor parameters to fetch subsequent pages without re-fetching all data.