goldapple-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GOLDAPPLE_CITY | No | Default city: a name from list_cities (e.g. Екатеринбург, case-insensitive, е = ё) or its FIAS id. | Екатеринбург |
| GOLDAPPLE_LEAN | No | 0 loads images, fonts and third-party scripts too (≈0.5 GB more memory; not needed for the check). | 1 |
| GOLDAPPLE_PROXY | No | Proxy for the browser, e.g. http://user:pass@host:3128 | |
| GOLDAPPLE_HEADLESS | No | 0 shows the browser window (debugging; downloads full Chromium if missing). | 1 |
| GOLDAPPLE_CACHE_DIR | No | Browser profile (anti-bot cookies — treat it as a secret; directory 0700, files 0600), city list, IP location. | ~/.cache/goldapple-mcp |
| GOLDAPPLE_IDLE_TIMEOUT | No | Seconds without calls before the browser is closed. | 600 |
| GOLDAPPLE_MIN_INTERVAL | No | Seconds between requests to the site (minimum 0.5). Keep it: the anti-bot scores bursts. | 2.0 |
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_productsA | Search goldapple.ru like the site does: real pages, sorting and a guest-price window. Per item: item id, URL, brand, name, product type, the size/shade the tile
lists (its price is for that variant — |
| browse_categoryA | List a goldapple.ru category page with the site's sorting and guest-price window. Items have the same fields as search_products. Unlike search, a category is
not capped at 2000 results; |
| get_productA | Full product card for one item id, live for the city. Returns every variant (size/shade) with its guest and signed-in price,
|
| get_reviewsA | Buyer reviews: date, stars, the size/shade bought, pros, cons, comment, photo count, likes. Page 1 also returns the line rating and star split (always for all sizes/shades — the site has no per-variant rating) and how many reviews this variant has. Authors' names are never returned. |
| compare_productsA | Side by side for up to 10 items: variant, both prices, stock, line rating, cheapest delivery. The site has no batch endpoint, so each item costs three calls (~6 s); items that fail are listed with the reason. |
| list_citiesA | The cities goldapple.ru offers in its city picker (name, FIAS city id, region id). Any of them can be passed as |
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 6 tools
Each tool has a clearly distinct purpose: search_products (query-based), browse_category (category paging), get_product (single card), get_reviews, compare_products (multi-item), list_cities. The search/browse pair is the closest overlap, but descriptions explicitly call out their different behaviors (2000-cap vs has_more, query vs category).
All six tools follow a consistent snake_case verb_noun pattern (compare_products, list_cities, search_products, browse_category, get_product, get_reviews) with plain, predictable verbs. No style mixing.
Six read-only tools is well-scoped for a product-discovery surface, covering the discovery-to-detail path without redundancy. Nothing feels padded or missing at this size.
The read-only lifecycle is largely covered: discover (search/browse), detail (get_product), reviews, cross-item comparison, and city scoping. Cart/checkout and delivery-cost calculation are absent, but that's plausibly out of scope, leaving only minor gaps.