mcp-drizly
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 |
|---|---|
| search_productsB | Search for beer, wine, spirits, and other alcoholic beverages on Drizly by name, type, or brand |
| get_product_detailsB | Get detailed information about a specific product including ABV, origin, ratings, and pricing |
| browse_categoriesC | Browse Drizly products by category (beer, wine, spirits) and subcategory (IPA, Chardonnay, Bourbon, etc.) |
| check_availabilityB | Check if a product is available for delivery to a specific address and see which stores carry it |
| add_to_cartC | Add a product to the shopping cart |
| get_cartB | View the current shopping cart contents and totals |
| update_cartC | Update the quantity of an item in the cart or remove it (set quantity to 0) |
| get_storesB | Get available stores and retailers that can deliver to a specific address |
| place_orderC | Complete checkout and place the order for items in the cart |
| get_ordersB | View order history including past and current orders |
| track_orderB | Track the current status and estimated delivery time of an order |
| get_recommendationsC | Get personalized product recommendations based on preferences and order history |
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
Every tool has a clearly distinct purpose with no ambiguity. The tools cover different aspects of the shopping workflow (browsing, searching, cart management, ordering, tracking) without overlap. For example, 'add_to_cart' and 'update_cart' are complementary but distinct operations.
All tools follow a consistent verb_noun naming pattern throughout (e.g., 'add_to_cart', 'browse_categories', 'get_orders'). The verbs are descriptive and appropriate for each action, with no mixing of conventions or styles.
With 12 tools, this server is well-scoped for an e-commerce alcohol delivery platform. Each tool earns its place by covering essential functions like product discovery, cart management, ordering, and tracking, without being overly sparse or bloated.
The tool set provides complete coverage of the domain, including product browsing/searching, cart CRUD operations (add, update, get), ordering (place, track, get history), and supporting functions like availability checks and recommendations. There are no obvious gaps that would hinder agent workflows.