Czech DIY Retail MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MCP_HOST | No | Bind host for HTTP server | 0.0.0.0 |
| MCP_PATH | No | MCP endpoint path | /mcp |
| MCP_PORT | No | Bind port for HTTP server | 8000 |
| DIY_MAX_RESULTS | No | Maximum search results per retailer | 50 |
| DIY_HTTP_TIMEOUT | No | HTTP request timeout in seconds | 15.0 |
| DIY_CACHE_STOCK_TTL | No | Stock lookup cache TTL (seconds) | 60 |
| DIY_CACHE_STORE_TTL | No | Store list cache TTL (seconds) | 86400 |
| DIY_CACHE_SEARCH_TTL | No | Search cache TTL (seconds) | 120 |
| DIY_CACHE_PRODUCT_TTL | No | Product detail cache TTL (seconds) | 600 |
| DIY_MAX_CONCURRENT_PER_RETAILER | No | Max concurrent requests per retailer | 2 |
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
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_productsC | Search products across Czech DIY retailers (bauhaus, hornbach, obi, baumax, all). |
| get_productB | Get detailed product information by product ID / SKU. |
| list_storesC | List physical stores for a retailer with optional query filter. |
| get_stockA | Get current product stock level at a specific physical store branch. |
| compare_priceA | Compare product prices across DIY retailers, sorted ascending by price. |
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 targets a clearly distinct task: searching, fetching product details, listing stores, checking stock, and comparing prices. There is no meaningful overlap between these operations.
All tool names follow the same snake_case verb_noun pattern, such as search_products, list_stores, and compare_price. The naming is predictable and easy to understand.
Five tools is well-scoped for a retail-focused API covering search, product details, store locations, stock, and price comparison. Each tool serves a clear purpose without unnecessary bloat.
The tool set covers the core read-only workflows for a DIY retail assistant: discover products, inspect details, find stores, check availability, and compare prices. Minor gaps like browsing categories or fetching stock across all stores at once are not critical for the stated domain.