Raley
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
} |
| prompts | {
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| dealsA | Best-value items this week: clipped coupons + sale prices + price history. Run after 'offers sync'. |
| memoryB | Read or write shopping memory: T1D config, notes, preferences. Persists across sessions. |
| searchC | Search products. Returns best match with SKU, price, unit pricing. |
| addC | Add to cart. Need SKU and price_cents from search. |
| removeB | Remove from cart by SKU. |
| cartB | View cart. Supports summary_only, save_to_file, and limit options. |
| offersD | Coupons. action: list|clip_all|sync. |
| planC | Parse grocery list, find matches. Does not add to cart. |
| priceC | Price history by SKU, search local DB, or clear cache. Use clear=true when user changes store/delivery location. |
| ordersD | Order history. |
| favoritesC | Purchase history from 'previously purchased' API. |
| authA | Check authentication status (no cookie values exposed). |
| knowledgeA | Search installed T1D reference books: GI tables, insulin math, carb counting, recipes, meal planning. Use when the user asks about nutrition science, insulin timing, or needs recipe ideas. |
| read_savedA | Read a previously saved result file (from save_to_file=true). Returns the JSON contents. |
| add_planA | Bulk add items to cart. Pass comma-separated 'sku:cents' or 'sku:cents:qty' pairs. |
| storeB | View/change fulfillment store and delivery address. Prices and availability depend on the fulfillment store. |
| search_batchA | Search multiple products at once. Returns best match per query. Use instead of calling search N times. |
| cart_diffA | Compare a list of expected SKUs against the actual cart. Shows missing, extra, and quantity mismatches. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| weekly_deals | Surface this week's best Raley's deals: clipped coupons + sale items + price history context |
| t1d_meal_plan | Build a T1D-optimized weekly meal plan and shopping list based on current deals and user memory |
| seasonal_now | What California produce is in season right now at Raley's, with GI ratings and meal ideas |
| coupon_matchup | Cross-reference clipped coupons against order history — find stack deals and expiring offers |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 18 tools
Most tools have clearly distinct purposes: search/add/remove/cart handle core shopping, while deals/offers, price, plan, orders, favorites, and knowledge cover different aspects. A few pairs overlap conceptually (search vs search_batch, add vs add_plan, deals vs offers), but descriptions clarify when to use each.
Tool names mix single-word nouns (deals, cart, offers, store, memory, knowledge) with imperative verbs (search, add, remove, plan) and compound verb_noun forms (cart_diff, add_plan, search_batch). There is no consistent naming convention, which makes the set feel less predictable.
With 18 tools, the server is on the heavier side but each tool addresses a specific need in the grocery shopping workflow. The count is justified given the breadth of features (product search, cart management, deals, price history, planning, memory, and account functions).
The tool surface covers core grocery tasks well: searching, adding/removing/viewing cart, bulk operations, deal retrieval, price history, order history, favorites, store selection, and user preferences. Minor gaps exist (e.g., no direct quantity update tool, no checkout/order placement), but they are workable and the domain is well represented.