Skip to main content
Glama
sven-borden

galaxus-mcp

by sven-borden

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
GALAXUS_PORTALNoThe portal to use: galaxus or digitecgalaxus
GALAXUS_LANGUAGENoLanguage for product names and labels: en, de, fr, iten

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

CapabilityDetails
tools
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
galaxus_searchA

Full-text product search across the shop. Returns matching products with prices, ratings and availability, plus the facets (brand, category, price range, specs) that can be fed back in as filters to narrow the search.

galaxus_get_productA

Full detail for one product: price and previous price, availability and stock, rating, full specifications, variants, price-history summary, warranty and return policy. Accepts a numeric product id or a Galaxus product URL.

galaxus_autocompleteA

Fast type-ahead lookup. Returns search-term suggestions (with the categories they map to) and a handful of directly matching products. Useful to resolve a vague phrase into a concrete product or category before searching.

galaxus_browse_categoryA

List products in a category (product type) without a search term — the equivalent of opening a category page. Category ids come from galaxus_search results (category_id), the pt facet, or galaxus_autocomplete.

galaxus_browse_brandA

List products from one brand. Brand ids come from the bra facet returned by galaxus_search or galaxus_browse_category.

galaxus_related_productsA

Products related to a given one: similar for alternatives to compare against, bought_together for complements, accessories for add-ons.

galaxus_get_review_summaryA

What customers think of a product: the average rating, how many people rated it, and the pros and cons reviewers mention most often. Individual review texts are not exposed by the shop's API.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A4.1/5.0

Scored across 7 tools

Disambiguation5/5

Each tool has a clearly distinct purpose: autocomplete for suggestions, search for query-based results, get_product for details, browse_category and browse_brand for filtered browsing, related_products for discovery, and review_summary for ratings. There is no overlap; even browse_category and browse_brand are distinguished by their governing attribute (category vs. brand).

Naming Consistency4/5

All tools share the 'galaxus_' prefix, which aids recognition. However, after the prefix the pattern varies: 'search' and 'autocomplete' are bare verbs, 'get_product' and 'get_review_summary' use get_noun, 'browse_category' and 'browse_brand' use verb_noun, while 'related_products' is a noun phrase without a verb. This is a minor deviation that is still predictable and readable.

Tool Count5/5

Seven tools is an ideal size for a product information server—small enough to be easily navigable, yet comprehensive enough to cover search, browsing, retrieval, and related recommendations. Each tool fills a distinct niche without redundancy.

Completeness4/5

The tool set covers the core workflow of product discovery: autocomplete, search, browse by category/brand, full details, related items, and review summaries. A minor gap is that you cannot enumerate all categories or brands independently without first performing a search, but facet-based access is a reasonable design. No dead ends appear for typical shopping research.

Maintenance

ActivityStale
ResponsivenessNo issues