This server has severe definition quality issues. All 12 tools lack proper English descriptions (descriptions are in Turkish, which violates LLM-optimization principles). Tool names use underscores but lack action verbs in most cases (e.g., 'sehir_hava_ozet' instead of 'get_weather_summary'). Input schemas are present but minimal, most parameters lack detailed descriptions explaining format, constraints, or valid ranges. No output schemas are documented. Error handling is absent from visible code. The server appears to be a teaching/demo project rather than production-grade tooling.

• Translate all tool descriptions and parameter descriptions to English. Use clear, concise English (50 - 200 chars per tool description) optimized for LLM comprehension. Example: 'kdv_hesapla' → 'calculate_vat' with description 'Calculate VAT (Value Added Tax) on a net amount. Returns gross total. Requires net amount and VAT rate (e.g., 0.20 for 20%).'
• Rename all tools to start with action verbs. Use verb_noun pattern: 'sehir_hava_ozet' → 'get_weather_summary', 'kisa_ozet' → 'summarize_text', 'kelime_anlami' → 'explain_term', 'sistem_kontrol' → 'check_system_health'.
• Add detailed parameter descriptions including format, constraints, and valid ranges. Example: 'city' parameter → 'City name (string, 1 - 100 chars, e.g., Istanbul). Must be a valid Turkish city.'
• Document output schemas for all tools. Specify response structure, field types, and required fields. Example: 'calculate_vat returns {gross_amount: number, vat_amount: number, rate: number}'.
• Implement error handling with actionable recovery messages. Return structured errors like '{error: "Invalid city", message: "City not found. Try: Istanbul, Ankara, Izmir", retryable: false}' instead of raw exceptions.