cookwith-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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| generate_recipeC | Generate a new recipe based on natural language instructions |
| transform_recipeB | Transform or modify an existing recipe |
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
Both tools have clearly distinct purposes: generate_recipe creates new recipes from instructions, while transform_recipe modifies existing ones. No overlap or ambiguity.
Both tools follow a consistent verb_noun pattern: generate_recipe and transform_recipe, with clear and predictable naming.
Only 2 tools for a cooking assistant is too few; typical CRUD operations like list, get, delete are missing, making the surface feel thin.
The tool set lacks basic operations such as listing, searching, or deleting recipes, leaving significant gaps in expected functionality for a recipe management server.