cook-tool
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| XBY_APIKEY | Yes | 你的实际apikey (Your actual API key) |
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 |
|---|---|
| get_all_dishesB | 获取所有可用菜品的名称列表 (菜单)。 |
| get_dish_contentC | 根据提供的菜品名称获取其详细内容。 |
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 2 tools
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.
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.
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.
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.