ezmcd-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| EZMCD_DATA_DIR | No | Directory where accounts, credentials, and logs are stored. Defaults to ~/.local/share/ezmcdonalds. | ~/.local/share/ezmcdonalds |
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| capabilitiesA | Report implemented features and explicitly unverified or unsupported flows. |
| account_connection_instructionsA | Explain local enrollment; do not paste session files, SMS codes, or tokens into chat. |
| accounts_listA | List connected aliases and local spending limits without exposing credentials. |
| account_checkB | Verify the account session now and return wallet balance; never pays. |
| account_refreshA | Maintain an existing session without SMS or purchases. May rotate credentials. Repeated calls within 24h only verify; an unknown refresh outcome requires local login. Does not renew checkout runtime. |
| stores_favoritesB | Read this account's saved pickup restaurants. |
| store_getC | Read a seven-digit restaurant code; availability is checked again for pickup time. |
| pickup_slotsB | Get currently available pickup dates, times, and meal periods for a store. |
| menu_listC | Browse a live store/time menu, including card offers. Displayed prices are not final quotes. |
| product_detailC | Read live combo rounds, component choices, extra prices and supported standard configurations. No cart/order mutation. |
| cart_getB | Inspect exact products, quantities and combo choices currently selected in the official cart. |
| cart_add_simpleB | Add simple uncustomized menu items to an empty cart once. No order/payment; complex combos require official App configuration. |
| cart_add_configuredA | Add selected items/combos to an EMPTY cart once. Use live offer_id and explicit round/items choices from product_detail. Standard modifiers only. Does not order or pay; call checkout_quote next. |
| checkout_quoteA | Validate the current cart, components, discounts, locker/time, wallet and price cap; create a 120-second quote. |
| checkout_submitB | REAL PURCHASE: create and McWallet-pay one fresh quoted order within the locally authorized policy. Repeated calls only reconcile. |
| order_payA | Pay an existing locally CREATED order only if payment has never been attempted. All other states only query. |
| order_statusC | Reconcile the exact order, cashier and wallet. Never resubmits or consumes; cancellation overrides historical PAID. |
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 17 tools
Most tools target clearly distinct resources or actions, and the descriptions explicitly clarify boundaries around account, cart, and checkout. The closest overlap is between order_pay and checkout_submit because both involve real payment, but the existing-order versus fresh-quote distinction is stated.
All names use snake_case and are mostly resource_action, but the pattern is mixed: accounts_list and stores_favorites use plural resources while account_check and store_get use singular, and several names are noun_noun (order_status, product_detail). The conventions are readable but not fully consistent.
17 tools is slightly above the typical 3–15 range, but the domain has several separate stages—account, store/menu, cart, checkout, payment/status—so each tool is largely justified. It is on the heavy side but not excessive for a safety-critical ordering workflow.
The core purchase flow is covered from account check through menu, cart, quote, payment, and status. However, cart editing is limited to add-only operations with no remove/update/clear, and there are no tools for order cancellation, order history, or store search/favorites management.