HowToCook-MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| mcp_howtocook_getAllRecipesC | 获取所有菜谱 |
| mcp_howtocook_getRecipesByCategoryC | 根据分类查询菜谱，可选分类有: 水产, 早餐, 调料, 甜品, 饮品, 荤菜, 半成品加工, 汤, 主食, 素菜 |
| mcp_howtocook_recommendMealsC | 根据用户的忌口、过敏原、人数智能推荐菜谱，创建一周的膳食计划以及大致的购物清单 |
| mcp_howtocook_whatToEatB | 不知道吃什么？根据人数直接推荐适合的菜品组合 |
| mcp_howtocook_getRecipeByIdB | 根据菜谱名称或ID查询指定菜谱的完整详情，包括食材、步骤等 |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
Each tool has a clearly distinct purpose: getAllRecipes retrieves all recipes, getRecipeById fetches a specific recipe, getRecipesByCategory filters by category, recommendMeals creates personalized meal plans, and whatToEat suggests immediate meal combinations. There is no overlap or ambiguity in functionality.
All tool names follow a consistent snake_case pattern with the prefix 'mcp_howtocook_' and descriptive verb_noun combinations (e.g., getRecipeById, recommendMeals). The naming is uniform and predictable across all tools.
With 5 tools, the server is well-scoped for a cooking/recipe domain. Each tool serves a specific, valuable function without redundancy, making the count appropriate and manageable for the intended purpose.
The toolset covers core operations like retrieval, filtering, and recommendation effectively. However, there are minor gaps in CRUD coverage, such as no tools for creating, updating, or deleting recipes, which could limit full lifecycle management but are not essential for a read-only or recommendation-focused server.