CookLikeHOC MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| COOKLIKEHOC_DIR | Yes | The absolute path to the locally cloned CookLikeHOC repository. |
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_recipesA | 按菜名、食材或关键词检索本地 CookLikeHOC 菜谱,并返回上游来源链接。 |
| get_recipeA | 按 search_recipes 返回的路径读取完整菜谱;始终返回原始上游来源链接。 |
| list_categoriesA | 列出本地 CookLikeHOC 检出中的菜谱分类和数量。 |
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 3 tools
Each tool has a clearly distinct role: search_recipes finds recipes via query, get_recipe retrieves a specific recipe by path, and list_categories provides an overview of categories and counts. No functional overlap exists.
All tool names follow a consistent verb_noun pattern with snake_case: search_recipes, get_recipe, list_categories. This is uniform and predictable.
With only 3 tools, the set is well-scoped for a read-only recipe lookup server. Each tool provides a core function (search, retrieve, browse categories) without unnecessary bloat.
The core read workflows (search, get full recipe, list categories) are covered. A minor gap is the inability to list all recipes in a category directly, but the search tool may partially compensate through keyword search.