Barkeeper
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| BARKEEPER_HOST | No | Interface to bind | 127.0.0.1 |
| BARKEEPER_PORT | No | Port to bind | 8000 |
| BARKEEPER_DB_PATH | No | SQLite file path; use :memory: for a throwaway database | |
| BARKEEPER_TRANSPORT | No | Transport to use: stdio, http, or sse | stdio |
| BARKEEPER_ALLOWED_HOSTS | No | Comma-separated allowlist of hosts; enables DNS-rebinding protection | |
| BARKEEPER_ALLOWED_ORIGINS | No | Comma-separated allowlist of origins; enables DNS-rebinding protection |
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_inventoryA | List everything on the bar shelf, grouped by category. |
| add_itemA | Add one bottle, mixer, or garnish to the bar. Call this when the user buys or acquires something, once per item. Adding something already on the shelf just updates its category. |
| remove_itemA | Remove an item from the bar, because it ran out or was thrown away. |
| list_recipesA | List every saved recipe with its ingredients, but without the method. This is the cheap overview — use get_recipe for the full instructions of one drink. |
| get_recipeA | Get one recipe in full, with ingredients and the method. |
| save_recipeB | Save a cocktail recipe worth keeping, or update one already saved. |
| delete_recipeB | Delete a saved 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 7 tools
Each tool targets a distinct resource and action: inventory items (add, remove, list) and recipes (list, get, save, delete). There is no overlap or confusion between tools.
All tools follow a consistent verb_noun pattern using snake_case (remove_item, list_recipes, get_recipe, etc.). The verb clearly indicates the operation and the noun the target resource.
Seven tools is well-scoped for a bar management server covering both inventory and recipe management. Each tool has a clear purpose and none are redundant.
The surface covers full CRUD for recipes (list, get, save, delete) and essential operations for inventory (add, remove, list). The add_item tool also handles updates via category refresh, so no major gaps exist.