kundeavis-mcp
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": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_offersA | Search this week's Norwegian grocery offers. Free-text matches the product heading; filters narrow by ingredient, category, chain, unit-price basis and discount. Results are sorted cheapest-first by unit price. ALWAYS read unit_price together with unit_price_basis — a kr/kg and a kr/stk figure are not comparable — and treat unit_price_confidence='computed' as not cross-checked against the printed flyer. |
| cheapest_by_categoryA | The primary meal-planning entry point: cheapest offers per ingredient, grouped and ranked by unit price. Only kg and l bases are included, because per-piece prices cannot be ranked against them. Omit |
| compare_ingredientA | Price one ingredient across every chain this week, with a baseline from earlier weeks. Two distinct fields: |
| price_historyA | Cheapest unit price per week per chain for one ingredient, so you can judge whether a 'tilbud' is genuinely good. History only goes back as far as this installation has been syncing. |
| find_storesA | Grocery stores near a coordinate, nearest first. Offers are chain-national — the source API carries no per-store pricing — so this answers 'which shop do I go to' for a chain whose offer you already picked. |
| list_chainsB | Chains covered, with this week's offer counts and how many carry a usable unit price and an ingredient tag. Use it to see what coverage a meal plan can rely on. |
| syncA | Re-fetch the current flyers from the upstream API. Runs automatically when the current week is missing, so you rarely need to call it — use it to pick up a mid-week update. |
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
Most tools have clearly distinct purposes: search/compare/history/cheapest all target prices but from different angles (single scan vs cross-chain vs cross-week vs ranked summary). cheapest_by_category and search_offers overlap somewhat (both surface cheap offers), though category vs free-text search differentiates them reasonably. price_history vs compare_ingredient also share some ground but split time-series from current-week cross-chain.
Naming follows a consistent verb_noun pattern (search_offers, compare_ingredient, find_stores, list_chains, price_history). The two outliers are cheapest_by_category (adjective_noun preposition) and sync (single verb), which break the pattern but are still readable and not confusing.
Seven tools is a well-scoped surface for a grocery-offer MCP server. Each covers a meaningful concern: discovery, ranking, cross-chain comparison, history, store lookup, chain coverage, and data refresh. No tool feels superfluous.
The domain is grocery-offer lookup and meal planning, and the surface covers it thoroughly: search, cheapest-ranking, cross-chain comparison, historical baseline, store proximity, chain coverage, and upstream sync. The only minor gap is no explicit per-season/weekly API refresh trigger beyond sync, but sync covers data freshness.