Superzoo MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SUPERZOO_HOST | No | HTTP bind hostname or IP. Defaults to 127.0.0.1. | 127.0.0.1 |
| SUPERZOO_PORT | No | HTTP port, 1–65535. Defaults to 3000. | 3000 |
| SUPERZOO_COUNTRY | No | Country/shop to use: SK, CZ, or PL (case-insensitive). Defaults to SK. | SK |
| SUPERZOO_TRANSPORT | No | Transport mode: stdio or http. Defaults to stdio. | stdio |
| SUPERZOO_ALLOWED_HOSTS | No | Comma-separated accepted HTTP hostnames/IPs, without port or scheme. Defaults to loopback names/IPs plus the specific bind host. | |
| SUPERZOO_ALLOWED_ORIGINS | No | Comma-separated exact HTTP(S) browser origins allowed for CORS; no wildcards. Defaults to empty. |
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_productsB | Find Superzoo products in Slovakia, with public online EUR offers and availability summaries. Default 10, max 50 results. Search checks up to 200 mixed candidates; upstream totals are not product counts. Partial detail failures are marked on each product. Use variant-specific product IDs for stock lookups. |
| get_productB | Get product details, variants, public online EUR offers in Slovakia, delivery availability and available-store count. Price variant identifies conditional offers such as familyPrice; membership eligibility and branch prices are not verified. |
| get_product_availabilityA | Get availability in Slovakia stores for one product variant. Optional city filters store name/address locally, ignoring accents. Stock status and pickup text are separate. No exact quantities or branch prices. Check checked_at for freshness. |
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 3 tools
search_products, get_product, and get_product_availability target distinct actions (discovery, detail, store-level stock), and the descriptions clarify that get_product includes only availability summaries while get_product_availability is for one variant's store availability. There is mild overlap around availability, but the variant-specific scope of get_product_availability makes the boundary workable.
All three names follow a consistent snake_case verb_noun pattern: search_products, get_product, get_product_availability. The shared get_product prefix also makes the detail/availability relationship predictable.
Three tools are reasonable for a focused read-only product catalog: search, detail, and availability. The surface is slightly thin, but each tool has a clear role and the server does not appear to need broader mutation operations.
The core read-only product workflow is covered: find products, inspect product details and variants, and check store availability for a variant. Minor gaps exist, such as no standalone store listing or category browsing, but agents can work around these through search and product details.