goodbook-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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_food_standardsC | Search for specific food preparation standards, recipes, or cooking guidelines in the food service literature |
| get_cooking_guidelinesC | Get cooking guidelines and standards for specific dishes or cooking methods |
| list_sectionsB | List all available sections in the food service standards document |
| get_section_contentC | Get content from a specific section of the food standards document |
| get_food_safety_infoC | Get food safety information and hygiene standards |
| find_recipe_standardsC | Find standardized recipes and preparation methods for specific dishes |
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 6 tools
There is significant overlap between tools like find_recipe_standards, get_cooking_guidelines, and search_food_standards, which all seem to retrieve similar types of information about recipes, guidelines, and standards. However, the descriptions provide some differentiation, such as get_food_safety_info focusing on safety/hygiene and list_sections/get_section_content being more structural. The overlapping purposes could lead to confusion when selecting the right tool for a query.
The tool names follow a consistent verb_noun pattern with snake_case throughout, such as find_recipe_standards and get_cooking_guidelines. All tools start with verbs like 'find', 'get', 'list', or 'search', which is predictable and readable. There are no deviations in naming conventions, making it easy to parse the tool set at a glance.
With 6 tools, the count is well-scoped for a server focused on food service standards and recipes. This number is neither too thin nor too heavy, allowing for a focused set of operations without overwhelming an agent. Each tool appears to serve a distinct purpose within the domain, making the count appropriate for the server's apparent scope.
The tool set covers core operations for accessing food standards, recipes, safety info, and document structure, providing good coverage for retrieval and search within the domain. However, there are minor gaps, such as no tools for updating or managing standards (e.g., create or modify operations), which might limit agents in more dynamic workflows. Overall, it supports essential querying tasks effectively.