tweakers-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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_productsA | Search Tweakers Pricewatch by name or SKU. Returns at most ~8 matches (product_id, name, url, price when known). Use product_id with the other tools. |
| get_productA | Product info (brand, name, mpn, gtin, price range) plus the cheapest shop
offers. |
| get_cheapest_offersA | Cheapest current shop offers for a product, sorted by total price
(product + shipping). Includes shop name, product_price, shipping_cost,
condition and url. Refurbished/open-box/outlet offers are left out (counted in
|
| get_specsC | Full specification table of a product as {group: {label: value}}. |
| find_cheapestA | Search for a product and return the best match with its specs and cheapest
offers in one call. Takes the first of the top 3 hits that has usable shop
offers (falls back to the first hit). Other search hits are returned as
|
| get_category_filtersA | Spec filters available in a category (e.g. 'koelkasten'): name, kind
('select' with options, or 'range' with min/max values). |
| browse_categoryA | Browse a Pricewatch category (e.g. 'videokaarten', 'koelkasten'), optionally
filtered server-side by specs, so only matching products are returned.
sort: 'prijs' | 'popularity' | 'score'; sort_dir: 'asc' | 'desc'.
filters: {filter name: value}, names/options from get_category_filters, e.g.
{"Energieklasse (2021)": ["A"], "Geluidssterkte (max.)": {"max": 29}}
select filters take an option label or list of labels; range filters take
{"min": x, "max": y} (inclusive bounds).
details: for the first N items also return full specs and cheapest offers
(one extra request each; keep small). Refurbished/open-box/outlet offers are
left out of those offers (counted in |
| list_categoriesB | Category slugs mapped to names; |
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 8 tools
get_product, get_cheapest_offers, and find_cheapest all return shop offers for a product, creating overlap; get_product already includes offers that get_cheapest_offers returns alone. Descriptions do differentiate intent (info vs offers vs convenience bundle), but an agent must reason carefully to pick the right one.
All names are snake_case verb_noun (search_products, get_product, browse_category, list_categories), which is predictable. The verb set varies (search/get/find/browse/list), causing minor deviation from a single canonical verb pattern.
Eight tools is well-scoped for a price-comparison server: search, product detail, offers, specs, category browsing, filters, and categories. Each tool earns its place in the workflow.
Covers the core Pricewatch lifecycle: discover categories, filter, search, fetch specs and offers. Minor gaps exist (no price-history or direct product-comparison tool), but agents can work around these with the current surface.