Polyglot MCP has complete input schemas for all 6 tools with proper JSON Schema structure and type definitions. However, descriptions are in Polish and lack LLM-optimized English guidance. Most parameter descriptions are missing or minimal. No output schemas are documented. Error handling is absent from tool definitions. Tool naming follows verb_noun convention (get_, set_, create_, update_) which is good, but descriptions do not explain WHEN to use each tool or what the LLM should expect in return. The server is STDIO-only, which caps protocol readiness at 50 regardless of definition quality.

• Translate all tool descriptions to English and expand to 50-200 characters, following the pattern: 'WHAT does it do? WHEN should the LLM call it? WHAT does it return?' E.g., 'get_stats: Retrieves learning statistics for a language. Call at session start to check progress. Returns word counts, accuracy rates, and next review dates.'
• Document output schemas for all tools. Add a 'returns' field to each tool definition showing the structure of the response (e.g., get_stats returns {language: string, total_words: number, due_today: number, accuracy: number}).
• Add descriptions to all input parameters, especially enums. For set_language_profile.action, explain: 'create: new profile, update: modify existing, switch: activate different language, deactivate: pause learning.'
• Implement error handling in tool implementations and return structured error responses with recovery guidance. E.g., 'Language code invalid. Supported codes: zh, ja, es, de. Try again with a valid code.'
• Add idempotency keys or dry-run modes to write operations. E.g., create_word_note could accept a 'dry_run' parameter to validate before writing, or return a confirmation token for multi-step operations.