This server has severe definition quality issues. It exposes only 1 tool (get_recipe_prompt) with an empty input schema and a vague, generic description. The tool's purpose is unclear: it returns a long German-language prompt text rather than performing a structured operation. There is no input validation, no parameter documentation, and no structured output schema. The tool reads more like a prompt-template delivery mechanism than an MCP tool. A tool that simply returns static text with no parameters fails to meet production quality standards.

• Redefine get_recipe_prompt() with a proper input schema. If the tool truly takes no parameters, explicitly document why (e.g., 'This tool retrieves a system-wide prompt and takes no user input'). If the tool should accept recipe data or context, add optional parameters (recipe_name, source_pdf_path, user_language) with type definitions and descriptions.
• Replace the German description with an English one that explicitly states: (1) What the tool does (returns a workflow prompt for recipe extraction), (2) When to use it (e.g., when initiating a recipe processing workflow), (3) What the LLM should do with the result (follow the prompt instructions, invoke dependent tools, etc.), (4) Any prerequisites (e.g., 'Requires access to filesystem, image-selector, recipe-index tools'). Target 50 - 150 characters.
• Document the output schema: Define the response as a structured object with fields like { "prompt": string, "version": string, "dependencies": [string], "language": string } instead of a raw text block. This allows the LLM to reason about the prompt's structure and metadata.
• Consider splitting this into two separate tools: (1) get_recipe_workflow_prompt() → returns the instructional prompt text (discovery/reference), and (2) process_recipe_pdf(pdf_path, user_language?) → orchestrates the full workflow described in the prompt. The current tool blurs the line between retrieval and execution.
• Add error handling documentation. Include recovery guidance: 'If the prompt cannot be retrieved, verify the server is properly initialized and has access to workflow templates. Retry with a short delay (1 - 2 seconds).'