Critical gaps across all dimensions. 10 tools with minimal descriptions (avg 35 chars, well below 194-char baseline). No input schemas visible for 6 tools (get_btc_cycle_regime, get_lth_behavior, get_entry_risk, compare_to_2021_top, get_nupl_sentiment, get_analyst_momentum). Only 4 tools show partial schemas with required args. No output schemas documented. No error handling guidance. Tool names are verb-prefixed but descriptions are generic placeholders. This server exposes financial analysis tools via a payment-gated proxy but provides almost no LLM-usable metadata.

• Add full input schemas to all 10 tools. For no-arg tools (get_btc_cycle_regime, get_lth_behavior, etc.), explicitly define 'input: {}' with description 'No parameters required.'
• Expand all descriptions to 100-200 chars. Example: 'get_btc_cycle_regime' → 'Analyze Bitcoin market cycle phase using on-chain metrics. Returns cycle stage (accumulation/markup/distribution/markdown), confidence score, and key indicators. Use to assess market timing and risk appetite.'
• Document output schemas for all tools. Specify returned fields, types, and what each represents. Example: 'Returns {cycle_stage: string, confidence: number 0-1, indicators: {metric: value}}'.
• Add parameter descriptions for ticker/ticker1/ticker2/tickers. Example: 'ticker: Stock ticker symbol (e.g., AAPL, TSLA). Must be 1-5 uppercase letters.'
• Implement error recovery guidance. Catch HTTP errors and return: 'MCP service unavailable. Retry in 30s or try a different analysis tool.' instead of raw 500 errors.