Skip to main content
Glama
xiaobenyang-com

cook-tool

README.md
# 菜谱查询工具 

一个支持通过命令行查询菜谱和报菜名的菜谱查询工具,适用于烹饪爱好者和开发者。
A recipe query tool that supports querying recipes and reporting dish names through the command line, suitable for cooking enthusiasts and developers.## 工具列表 Tool List

本MCP服务封装下列工具,可让模型通过标准化接口调用以下功能。 本MCP服务封装下列工具,可让模型通过标准化接口调用以下功能。

| 工具 Tool   | 描述 Description         |
|-------|--------------------|
| get_all_dishes | 获取所有可用菜品的名称列表 (菜单)。 |
| get_dish_content | 根据提供的菜品名称获取其详细内容。 |


## 检查服务 ## Inspector

工具在线测试: [https://mcp.xiaobenyang.com/inspector/1777316659522563](https://mcp.xiaobenyang.com/inspector/1777316659522563)

Online Tool test [https://mcp.xiaobenyang.com/inspector/1777316659522563](https://mcp.xiaobenyang.com/inspector/1777316659522563)

## 服务配置 MCP Server Config


> #### 如何获取 XBY-APIKEY ? How to get XBY-APIKEY ?
> 访问小笨羊科技网站 [https://xiaobenyang.com](https://xiaobenyang.com),注册用户即可获得APIKEY
> Visit XiaoBenYang website [https://xiaobenyang.com](https://xiaobenyang.com), register and get the APIKEY.

### SSE
```json
{
  "mcpServers": {
    "菜谱查询工具": {
      "headers": {
        "XBY-APIKEY": "<YOUR_XBY_APIKEY>"
      },
      "type": "sse",
      "url": "https://mcp.xiaobenyang.com/1777316659522563/sse"
    }
  }
}
```
### STREAMABLE HTTP
```json
{
  "mcpServers": {
    "菜谱查询工具": {
      "headers": {
        "XBY-APIKEY": "<YOUR_XBY_APIKEY>"
      },
      "type": "streamable_http",
      "url": "https://mcp.xiaobenyang.com/1777316659522563/mcp"
    }
  }
}
```
### STDIO
```json
{
    "mcpServers": {
        "菜谱查询工具": {
          "command": "npx",
          "args": [
            "-y",
            "xiaobenyang-mcp"
          ],
          "env": {
            "XBY_APIKEY": "<YOUR_XBY_APIKEY>",
            "mcpId": "1777316659522563",
          },
          "transport": "stdio"
        }
      }
}

```

TDQS

B3.1/5.0

Scored across 2 tools

Disambiguation5/5

The two tools have clearly distinct purposes: get_all_dishes retrieves a list of dish names (menu), while get_dish_content fetches detailed content for a specific dish based on its name. There is no overlap or ambiguity between these operations.

Naming Consistency5/5

Both tools follow a consistent verb_noun pattern with 'get_' prefix and snake_case naming (get_all_dishes, get_dish_content). The naming is predictable and readable throughout.

Tool Count2/5

With only 2 tools, the server feels thin for a cooking/recipe domain. It lacks essential operations like creating, updating, or deleting dishes, which limits its utility and scope. A minimal CRUD set would typically have at least 3-4 tools.

Completeness2/5

The tool surface is severely incomplete for a cooking domain. It only provides read operations (get all and get details), missing create, update, delete, search, or other lifecycle management tools. This will likely cause agent failures when trying to perform full workflows.

Maintenance

ActivityInactive
ResponsivenessNo issues