Restaurant Backend MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| BACKEND_URL | No | Override the backend URL. Default is http://localhost:8000 |
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": true
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {
"tasks": {
"list": {},
"cancel": {},
"requests": {
"tools": {
"call": {}
},
"prompts": {
"get": {}
},
"resources": {
"read": {}
}
}
}
} |
Tools
Functions exposed to the LLM to take actions
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| create_order_prompt | |
| track_order_prompt | |
| order_assistance_prompt |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| menu_resource |
TDQS
Scored across 24 tools
Most tools target distinct resources and actions, but get_orders_by_status and get_filtered_orders could overlap, and get_order_details vs get_order_journey might cause confusion.
Predominantly uses verb_noun snake_case, but inconsistencies like singular/plural (menu_items vs menu_item_details) and 'staff_login' (noun-style) break the pattern slightly.
24 tools cover multiple domains (menu, orders, customers, etc.) reasonably; slightly high but not excessive given the scope.
Covers CRUD for most entities but lacks delete operations for menu items, promotions, and reviews; minor gaps but overall comprehensive.