letu-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LETU_CITY | No | City name as on letu.ru (e.g., Екатеринбург, Москва). | the site's geo-IP city |
| LETU_PROXY | No | Proxy URL, e.g. http://user:pass@host:3128 | |
| LETU_CACHE_DIR | No | Where the anonymous session is kept (directory 0700, file 0600). | ~/.cache/letu-mcp |
| LETU_USER_AGENT | No | Override when the built-in one gets old (the site's firewall answers 403 to non-browser clients). | a current desktop Chrome UA |
| LETU_MIN_INTERVAL | No | Seconds between requests to letu.ru (plus up to 0.5 s jitter). | 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 letu.ru like the site does: pages, sorting, price window, seller and in-stock filters. Each item: product id and URL, brand, name, |
| get_productA | Full live card of one product: every variant with its price, the club-card split and delivery in the city. Per variant ( |
| get_reviewsA | Buyer reviews of a product: date, stars, text, pros, cons, likes, verified purchase, shop answer. Also returns the product rating (all variants together) with the star split. Reviews are not linked to a variant (volume/shade). Buyer names and order numbers are never returned. |
| get_store_availabilityA | Where one variant can be picked up in the city: stores with the site's stock level and pickup day. Stores are ЛЭТУАЛЬ shops ( |
| compare_productsA | Side-by-side rows for up to 10 products, one variant each. Per product: the pinned variant, or the cheapest one (orderable in the city
when |
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 distinct concern: search, product detail, reviews, store availability, and comparison. There is minimal overlap, and even the most similar tools (get_product vs compare_products) are clearly separated by purpose.
All tool names follow a consistent snake_case verb_noun pattern: search_products, get_product, get_reviews, get_store_availability, compare_products. The naming is predictable and makes the tool's action and target easy to identify.
Five tools is well-scoped for a retail product data server. Each tool covers a meaningful, non-redundant part of the shopping research flow without adding clutter or requiring excessive call chains.
The read-only product surface is well covered: search, full product details, reviews, store pickup, and comparison. Minor gaps exist such as no dedicated category/brand listing or bulk variant availability tool, but agents can accomplish the core workflows using the provided tools.