Server has 5 tools with complete input schemas and descriptions. All tools are read-only currency/exchange-rate operations. Naming is clear and verb-based (guncel_kur, tum_kurlar, kur_cevir, gecmis_kur, doviz_listesi). Descriptions are present and adequate (50-150 chars), explaining what each tool does. Input parameters have type definitions and descriptions. However, output schemas are not formally documented, responses are JSON strings without declared structure. Error handling returns JSON with 'hata' (error) fields but lacks recovery guidance. No tool annotations (readOnlyHint, etc.) despite all being read-only. Parameter descriptions could be more precise about constraints (e.g., date format validation, currency code validation). No pagination or result limits documented.

• Add readOnlyHint=true to all 5 tool definitions using FastMCP's @mcp.tool(readOnlyHint=True) decorator to signal safety.
• Document output schemas formally. Define the structure of JSON responses (e.g., guncel_kur returns {kod, isim, alis, satis, tarih}). Include in tool docstrings or via a schema registry.
• Enhance error messages with recovery hints. When currency not found, return: 'hata: "USD not found", ipucu: "Call doviz_listesi() to see valid codes."'
• Replace example-based parameter descriptions with formal constraints. Use enums for currency codes or add a pattern field for date validation (YYYY-MM-DD).
• Add a discovery tool or document valid currency codes in tool descriptions. Agents should not have to call doviz_listesi() to learn what codes are valid, hint it in guncel_kur and gecmis_kur descriptions.

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

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