hermes-marketplace-tools
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PROXY_URL | Yes | SOCKS5 proxy URL for RU-IP (e.g., socks5h://USER:PASS@pool.proxy.market:10000) |
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 |
|---|---|
| marketplace_searchA | Поиск товаров на Ozon и/или Wildberries. Возвращает нормализованную выдачу. Сформируй несколько запросов (с брендом и без, разные формулировки) для лучшего покрытия. Сравнение и выбор делай сам по полученным данным. |
| get_product_cardC | Полная карточка: характеристики, описание, URL изображений. |
| get_reviewsC | Отзывы о товаре. |
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
Each tool targets a distinct function: product details (get_product_card), reviews (get_reviews), and search (marketplace_search). There is no overlap or ambiguity.
Two tools follow a 'get_' pattern, but 'marketplace_search' deviates slightly by being noun_verb. The inconsistency is minor and readability remains high.
Three tools is a reasonable number for a focused marketplace-browsing server. The scope is narrow but well-defined; no tool feels superfluous.
The set covers search, product card retrieval, and reviews, but lacks mutation operations (e.g., add to cart, compare) and entity listing (e.g., categories). Gaps exist but core browsing workflows are covered.