Pyro Storefront MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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_fireworksB | Поиск пиротехники и салютов в каталоге pyro.ua по бюджету, калибру, количеству залпов и времени работы |
| get_firework_detailsA | Получить полные характеристики салюта (калибр, видео работы, время, безопасная дистанция, инструкция) |
| check_stock_availabilityA | Пакетная проверка доступности товаров на складе и расчет итоговой суммы заказа перед чекаутом |
| search_delivery_branchesA | Поиск отделений и почтоматов Новой Почты в указанном городе для доставки заказа |
| create_orderC | Оформление заказа в pyro.ua с мгновенной ссылкой на оплату картой (Monobank) или наложенным платежом |
| track_orderA | Отслеживание статуса готовности заказа и номера ТТН Новой Почты с защитой от перебора (DLP) |
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 maps to a distinct stage or resource: catalogue search, item details, stock validation, delivery branch lookup, order creation, and order tracking. The only potential overlap is between search_fireworks and get_firework_details, but their purpose is clearly separated by list-level vs. detail-level access.
All tools follow a consistent verb_noun snake_case pattern: get_, search_, check_, track_, create_. This makes the toolset predictable and easy to reason about, with no mixed conventions or vague generic verbs.
Six tools is well-scoped for a storefront server: search, details, stock, delivery, ordering, and tracking each earn their place. The surface is neither bloated nor too thin for the stated purpose.
The core customer journey is covered end-to-end: find products, inspect them, verify stock, choose a delivery branch, place an order, and track it. Minor gaps exist such as no explicit order details endpoint or cancellation flow, but agents can complete the main purchase workflow without dead ends.