A
licenseA
qualityD
maintenanceIntegrates with Yandex Market Partner API, providing search and execute tools for managing orders, returns, shipments, offers, prices, and other seller operations via natural language.
18
1
MIT
Yango Tech Retail MCP
by A1-x-Tech
Related Servers
Alternatives to Yango Tech Retail MCP
No user-submitted related servers found.
Related Servers
- AlicenseAqualityAmaintenanceYandex Market Partner API in your AI assistant: orders and returns, products and cards, prices and tariffs, reports, reviews and chats. 165 methods live in a YAML catalog the server executes, the agent searches it in plain language, and every method carries an access class so writes and irreversible calls ask for confirmation.2626 PyPI2MIT
- FlicenseAqualityCmaintenanceEnables AI agents to query orders, manage routes, track drivers, and analyze delivery performance on the FleetSync last-mile delivery platform through natural language.18-
- FlicenseBqualityBmaintenanceEnables AI assistants to query live pricing and stock, place and track orders, and retrieve invoices through Dicker Data's B2B partner/reseller REST API.9-
- AlicenseAqualityAmaintenanceEnables AI assistants to search products, manage a cart, and place orders with Yandex Lavka, requiring explicit human confirmation before charging.2222MIT
- AlicenseAqualityBmaintenanceEnables AI agents to manage inventory conversationally: list and look up products, check current stock levels, record inbound and outbound movements idempotently, review movement history, and surface items below their minimum threshold. Every figure is grounded in tool calls rather than model estimation, and invalid operations return explicit error codes the agent can reason about.5MIT
TDQS
A4.4/5.0
Scored across 16 tools
Disambiguation5/5
Each tool targets a distinct resource and action (price lists, orders, order state, events, receipts, stores, products, prices, discounts, stocks). Even similar tools like get_order and get_orders_state are clearly separated by their descriptions, making selection unambiguous.
Naming Consistency5/5
Tool names follow a consistent pattern: 'query_' for cursor-based feeds, 'get_' for direct retrieval, 'create_', 'set_', 'update_', 'cancel_' for writes, and 'raw_request' as an explicit escape hatch. The verbs are meaningful and consistent, with no mixed conventions.
Tool Count4/5
16 tools is slightly above the typical well-scoped range but appropriate for a comprehensive retail API that spans orders, catalog, pricing, inventory, discounts, and receipts. Each tool serves a distinct purpose, and the count feels justified rather than bloated.
Completeness4/5
Core workflows are covered with dedicated tools for order creation/cancellation/query, product listing/creation, price get/set, stock query/update, and discount creation. Some operations (e.g., order update, price list creation, product update) lack dedicated tools but are reachable via raw_request, so agents can work around minor gaps.
Maintenance
ActivityMaintained
ResponsivenessNo issues