MCPizza - Enhanced
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 | {
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| find_storesB | Find nearby Domino's stores by address or zip code. Returns store IDs, addresses, and phone numbers. |
| get_store_infoC | Get detailed information about a specific Domino's store including hours and services. |
| get_menuB | Get the full menu for a specific store. Returns all available items organized by category. |
| search_menuC | Search for specific menu items at a store. Can filter by category and search term. |
| create_orderB | Create a new order for delivery or carryout. Required before adding items. |
| add_item_to_orderB | Add a menu item to the current order. Must create an order first. |
| add_pizza_with_toppingsC | Add a customized pizza with toppings using a coupon code. Handles proper product + topping configuration. |
| view_orderB | View the current order including all items, prices, and totals. |
| clear_orderB | Clear the current order and start over. |
| get_couponsC | Get available coupons and deals for a store. Returns coupon codes, descriptions, and prices. |
| get_ordering_guidanceC | Get AI guidance on how to build the best order based on user preferences. Analyzes deals, suggests optimal pizza counts, and provides ordering strategy. |
| place_orderA | ⚠️ PLACES A REAL ORDER with real payment! Submit the current order to Domino's. Requires payment information. |
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 12 tools
Each tool has a clearly distinct purpose with no significant overlap. For example, 'get_menu' retrieves the full menu, while 'search_menu' filters it, and 'add_item_to_order' and 'add_pizza_with_toppings' handle different item types. The descriptions clearly differentiate their functions, making misselection unlikely.
All tool names follow a consistent verb_noun pattern using snake_case, such as 'create_order', 'get_menu', and 'place_order'. This uniformity makes the tool set predictable and easy to understand, with no deviations in naming style.
With 12 tools, the server is well-scoped for a pizza ordering domain. Each tool serves a specific role in the ordering workflow, from store lookup to order placement, without being excessive or insufficient for the intended functionality.
The tool set provides complete coverage for the pizza ordering domain, including store discovery, menu browsing, order creation and management, coupon retrieval, and final placement. There are no obvious gaps, as all essential CRUD and lifecycle operations are covered, ensuring agents can handle the full process without dead ends.