Critical gaps across all dimensions. Tool definitions lack proper schemas, descriptions are minimal or missing, and parameter documentation is sparse. 'wallet' and 'prism' tools have only a 'method' parameter with no enum or validation, making them opaque proxies rather than well-defined tools. No output schemas documented. Error handling is absent from tool definitions. Only 'register', 'login', 'verify' have basic descriptions; others are generic or incomplete. This server exposes MCP as a thin CLI wrapper without proper tool abstraction.

• Replace wallet and prism with explicit, named tools for each method (e.g., wallet_transfer, wallet_balance, prism_payment, prism_settlement). Document each with full schema and description.
• Add output schemas to all tools. Document return fields, types, and structure. Example: register returns {challenge_id, expires_at}, login returns {challenge_id, expires_at}.
• Expand descriptions to 50-200 chars. Include WHAT the tool does, WHEN to use it, and WHAT it returns. Example: 'Verify OTP code to complete login or registration. Required after calling login() or register(). Returns auth token and user profile.'
• For config tool, document action enum (set|get|unset|show), required parameter combinations, and behavior for each action. Add examples in description.
• Add error handling guidance to tool descriptions. Example: 'If OTP is invalid, returns error_code=invalid_otp with retry_count. Retry up to 3 times before asking user to request new code.'

Inferred effective spec: <=2025-11-25.

• Relies on Logging (deprecated) - log to stderr or use OpenTelemetry