galaxus-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GALAXUS_SITE | No | Site to use: galaxus.ch, galaxus.de, or digitec.ch | galaxus.ch |
| GALAXUS_PORTAL | No | X-Dg-Portal value (e.g., 22 for galaxus.ch) | |
| GALAXUS_LANGUAGE | No | Language code: en, de, fr, etc. | |
| GALAXUS_TIMEOUT_MS | No | Per-request timeout in milliseconds | 15000 |
| GALAXUS_USER_AGENT | No | User-Agent header sent with requests | |
| GALAXUS_SEARCH_HASH | No | Persisted query id for useSearchDataQuery | |
| GALAXUS_CACHE_TTL_MS | No | Response cache TTL in milliseconds | 60000 |
| GALAXUS_PRODUCT_HASH | No | Persisted query id for productDetailPageQuery | |
| GALAXUS_MIN_INTERVAL_MS | No | Minimum delay between requests in milliseconds | 800 |
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_productsA | Search the Galaxus / Digitec catalog by keyword. Returns matching products with price (CHF), rating, availability, and URL, plus a nextCursor for pagination. |
| get_productA | Fetch full details for a single product by its numeric id, slug, or full product URL: description, GTIN, specifications, images, rating, availability, and price history. |
| check_price_availabilityA | Lightweight price + stock snapshot for one product (id, slug, or URL), including price-history position (whether the current price is low/high vs the recent range). Ideal for price tracking. |
| compare_productsA | Fetch full details for several products at once (by id, slug, or URL) for side-by-side comparison. Returns one detail object per input. |
| list_categoryA | Browse products in a category by name (e.g. 'ssd', 'office chair'), sorted and filterable. Returns products plus facets (available brands and product types) to help refine, and a nextCursor for paging. |
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 5 tools
Each tool has a distinct purpose: search, browse by category, single product details, lightweight price check, and multi-product comparison. Some overlap exists between get_product, compare_products, and check_price_availability, but descriptions clearly differentiate them.
All tool names follow a consistent verb_noun pattern in snake_case: search_products, get_product, check_price_availability, compare_products, list_category. The naming is predictable and clear.
With 5 tools, the server is well-scoped for product discovery, detail retrieval, price tracking, and comparison. The count is within the ideal range and each tool earns its place.
The tool surface covers the core catalog lifecycle: search, category browsing, single product details, price/availability checks, and product comparison. Minor gaps like an explicit category listing or bulk search are missing, but agents can work around these.