mcp-wendys
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_menu_itemsA | Search Wendy's menu items by name, category, or keyword. Returns matching items with name, description, price, and category. |
| get_item_nutritionB | Get nutrition information and calorie count for a specific Wendy's menu item. |
| find_nearby_locationsA | Find nearby Wendy's restaurant locations based on an address or zip code. |
| add_to_orderB | Add an item to the current mobile order cart. |
| apply_offerA | Apply a promotional offer or deal code to the current order. |
| place_orderB | Place the current order at a selected Wendy's location. |
| check_order_statusA | Check the current status of a placed order. |
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 7 tools
Each tool targets a distinct stage of the Wendy's ordering flow: menu discovery, nutrition details, location lookup, cart management, offers, checkout, and order tracking. No two tools overlap in purpose, making selection unambiguous.
All tool names follow a consistent verb_noun pattern (search_, get_, find_, add_, apply_, place_, check_). The naming convention is uniform and predictable, aiding agent comprehension.
With 7 tools, the server is well-scoped for its purpose—covering the essential steps of finding, ordering, and tracking Wendy's food. Each tool earns its place without redundancy or bloat.
The tool surface covers the full order lifecycle from search to status check. A minor gap is the lack of an explicit remove-from-order tool, but agents can likely work around this by building a new order or using external logic.