Single tool with basic but incomplete definition. Tool name 'describe_recipe_options' follows verb_noun convention and is reasonably clear, but the description, while present, is somewhat generic and doesn't explain prerequisites or when to use it vs other tools. Input schema is present with proper type and required flag, but critically lacks parameter validation guidance (e.g., what constitutes a valid recipeId format). No output schema is documented, the tool returns a JSON string but the structure and fields are not formally declared, forcing LLMs to parse unstructured text. Error handling is minimal: errors are returned as text without recovery guidance or actionable next steps. The server is STDIO-only, which triggers a hard cap of 50, but the definition quality itself is marginally better, reaching 52 due to having a schema and description.

• Document output schema explicitly. Add a formal JSON Schema definition stating that the response contains 'recipeOptionsMetadata' (object with 'options' array, 'recipeId' string) and 'type' field. Include field descriptions so LLMs know what each field means.
• Add validation constraints to 'recipeId' parameter description: 'A non-empty string identifier for the recipe (e.g., alphanumeric, 2-50 characters). If you don't have a recipe ID, call list_recipes() first.'
• Enhance error messages with recovery guidance. Instead of 'Error describing options: ...', return structured errors like 'Invalid recipeId format. Expected alphanumeric string, 2-50 chars. Call list_recipes() to find valid recipe IDs.'
• Expand tool description to include WHEN and WHY: 'Call this tool before running a recipe to discover all available configuration options and their types. Returns option names, descriptions, types (string/boolean/number), and required flags. Call this first if the user mentions running a recipe but doesn't specify options.'
• Consider adding a companion tool (list_recipes or search_recipes) to help LLMs discover valid recipe IDs without guessing.
• Migrate from STDIO to Streamable HTTP transport for remote accessibility and compliance with current MCP spec (2026-07-28).