avasfood-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| AVAS_API_BASE | No | Owner-approved API override | |
| AVAS_STATE_DIR | No | Local private state override | |
| AVAS_ENVIRONMENT | No | Defaults to LIVE | |
| AVAS_ACCESS_TOKEN | No | Approved backend token, if required |
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 |
|---|---|
| get_client_metadataA | Return verified AVAS client/API metadata and MCP safety mode. |
| list_restaurantsC | List AVAS restaurants in a Maldives delivery zone; optionally filter by name. |
| get_restaurantB | Get public details for one AVAS restaurant by merchant ID. |
| search_menu_itemsB | Search public AVAS menu items across restaurants by name or description. |
| account_statusA | Show whether this MCP is linked to an AVAS customer account. |
| start_phone_loginC | Send an AVAS login OTP to an existing customer's Maldives phone number. |
| verify_phone_loginB | Verify the AVAS OTP previously sent by start_phone_login. |
| list_delivery_addressesA | List saved delivery addresses for the linked AVAS account. |
| get_menuC | Load a merchant menu using the linked customer and delivery context. |
| add_to_cartC | Add a canonical CartRow locally; a cart may contain only one merchant. |
| update_cart_itemB | Update local cart quantity; use remove_cart_item to delete. |
| remove_cart_itemC | Remove one local cart row. |
| view_cartA | View the persisted local cart. |
| clear_cartA | Clear local cart and checkout artifacts; no network request is made. |
| quote_cartB | Calculate an authenticated cart quote. This calls CalculationSalesOrder but never saves. |
| stage_receiptA | Validate and privately copy a PNG/JPEG receipt locally. Does not upload. |
| upload_receiptC | Upload the staged receipt only with the exact displayed confirmation phrase. |
| prepare_orderC | Freeze the current quote and order details into an immutable confirmation preview. |
| submit_orderA | Validate then place the frozen order exactly once. Ambiguous saves are never retried. |
| track_deliveriesB | List and track the linked customer's active AVAS orders and delivery state. |
| delivery_spending_reportC | Summarize recorded AVAS spending by restaurant, food type, and delivery fees. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| food_assistant | Safe conversational workflow for browsing, ordering, and tracking AVAS Food. |
| delivery_budget_analyst | Analyze local delivery spending without overstating historical coverage. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 21 tools
Each tool targets a distinct action or resource, such as cart operations, login steps, order management, and receipt handling, with no overlapping purposes.
Most tools follow a verb_noun pattern (e.g., add_to_cart, list_restaurants), though a few like account_status and delivery_spending_report deviate slightly, but the overall pattern is clear.
21 tools cover the full ordering lifecycle—login, restaurants, menu, cart, orders, receipts, deliveries—slightly above the ideal range but still well-scoped for a comprehensive food delivery service.
Core workflows are covered: login, restaurant browsing, menu search, cart management, quoting, order submission, delivery tracking, and receipt handling. Minor gaps like address management are absent but not critical.