Server has 5 tools with minimal schema definition and weak descriptions. Tool names follow verb_noun pattern (positive), but input schemas are severely incomplete. Most tools lack parameter descriptions entirely. Descriptions are present but generic and under 100 chars. No output schemas documented. Error handling exists but lacks recovery guidance.

• Define explicit JSON Schema for all tool inputs. For get_company_profile, add: {"type": "object", "properties": {"stock_code": {"type": "string", "pattern": "^[0-9]{6}$", "description": "6-digit stock code (e.g., 000001). Must be valid A-share code."}}, "required": ["stock_code"]}
• Expand tool descriptions to 80-150 chars with context. E.g., 'Fetch all A-share stocks (code, name, exchange). Use this first to discover available stocks before querying company profiles or capital trends.'
• Document output schemas for each tool. E.g., get_stock_list returns {"stocks": [{"code": string, "name": string, "exchange": string}], "total": number}. Include field types and which IDs can be passed to other tools.
• Add parameter constraints to descriptions. E.g., 'stock_code: 6-digit numeric string (e.g., 000001). Must be a valid A-share code listed on Shanghai or Shenzhen exchange.'
• Implement formal tool registration with explicit schemas instead of docstring parsing. Use a tool registry dict with name, description, input_schema, and output_schema keys.

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

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