kassalapp-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.
SIMULATED prices, not real ones: say so. Grocery prices per chain from Kassalapp. Read each 'say' aloud as it is. When the answer asks which product, read the choices and wait; never pick one. Then pass the chosen name or its 'ean' as 'product'. It only reads prices and never buys anything.
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 |
|---|---|
| grocery_priceA | What a grocery costs. The latest price per chain from Kassalapp, with the day it was checked. 'product' is the words the person said, such as 'lettmelk' or 'Tine lettmelk 1 liter', or the name or barcode ('ean') of a choice the last answer offered. 'chain' is a chain's name, such as 'Meny' or 'Joker'; omit it for every chain. |
| grocery_cheapestA | Which chain is cheapest? Ranks the chains by their current price from Kassalapp; a price unchecked for 14 days never counts. 'product' is the words the person said, such as 'kaffe', or the name or barcode ('ean') of a choice the last answer offered. |
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 2 tools
grocery_price returns per-chain prices for a product, while grocery_cheapest ranks chains by price — clearly different outputs, and the descriptions reinforce that. There is mild conceptual overlap since 'cheapest' is a derived view of the same price data, but the intended selection is unambiguous.
Both tools use the exact same snake_case pattern with a shared 'grocery_' prefix and a short descriptive suffix (price, cheapest). Fully predictable naming.
Two tools is thin for a price-comparison service: lookup and ranking are covered, but there is no search, chain listing, or history operation to round out the surface. It is defensible for a narrow purpose, but borderline sparse.
Core lookup by name/barcode and cheapest-chain ranking are present, but obvious gaps remain: no product search/discovery, no list-chains operation, and no price history or trend data. Agents can handle the main workflows but have no way to browse or resolve ambiguous queries.