cook-mcp
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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| logging | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| mcp_cook_getAllRecipesB | 获取所有菜谱 |
| mcp_cook_getRecipesByCategoryA | 根据分类查询菜谱，可选分类有: 水产, 早餐, 调料, 甜品, 饮品, 荤菜, 半成品加工, 汤, 主食, 素菜 |
| mcp_cook_recommendMealsA | 根据用户的忌口、过敏原、人数智能推荐菜谱，创建一周的膳食计划以及大致的购物清单 |
| mcp_cook_whatToEatA | 不知道吃什么？根据人数直接推荐适合的菜品组合 |
| mcp_cook_getRecipeByIdA | 根据菜谱名称或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
Most tools have clear distinct purposes: listing, filtering by category, detailed lookup, and two recommendation tools. The two recommendation tools (recommendMeals and whatToEat) overlap in intent, but their descriptions clarify that one is a simple combo picker and the other is a comprehensive planner with dietary constraints, so an agent can usually tell them apart.
All tools share a consistent 'mcp_cook_' prefix and use camelCase, but the action verbs are not uniform: 'getAll', 'getRecipes', 'recommend', 'whatToEat', and 'getRecipeById' mix verb-noun patterns and one non-verb phrase. Minor inconsistencies like 'Recipes' plural vs 'Recipe' singular further reduce naming consistency.
With 5 tools, the server is well-scoped for a recipe lookup and meal recommendation service. It is neither too sparse nor bloated, and each tool contributes a distinct capability for the domain.
The tool surface covers listing all recipes, filtering by category, retrieving full details, and two levels of meal recommendations, which addresses the core workflow of finding and choosing recipes. A minor gap is the lack of a dedicated tool to list available categories, though they are enumerated in the getRecipesByCategory description.