Skip to main content
Glama
dreamcatchered

Pyaterochka MCP Tool

by dreamcatchered
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to Pyaterochka MCP Tool

No user-submitted related servers found.

    Related Servers

    • globus-mcp

      toffguy77
      A
      license
      B
      quality
      B
      maintenance
      Enables LLM-driven interaction with the GLOBUS online store, including product search, catalog browsing, product details, promotions, recommendations, and anonymous shopping cart management via MCP.
      22
      MIT

    • shopmcp

      alexrexby
      A
      license
      Not graded
      quality
      B
      maintenance
      Turns an online store's catalog into MCP tools so agents can search products, fetch details, look up barcodes, analogs, categories, promotions and pickup points, and hand off a cart as a payment link rather than checking out. It is driven by a single TOML config with capability-based tool sets, bilingual model-facing texts, public catalog access plus OAuth 2.1-scoped personal tools like order history, and ready adapters for YML/Google Merchant feeds and WooCommerce across ten store engine presets.
      Apache 2.0

    • supermercado

      GTA7-Lab
      F
      license
      Not graded
      quality
      B
      maintenance
      Provides MCP tools to search products, check stock, and retrieve store information from the GTA7 Lab supermarket entity.
      -
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    C2.9/5.0

    Scored across 12 tools

    Disambiguation3/5

    Several tools overlap in purpose: find_store, find_nearest_stores, and list_stores_in_area all retrieve store locations but with different inputs, while get_store_info and get_store_hours both provide hours (though get_store_info is more comprehensive). Similarly, search_products, list_category_products, and find_products all search products with overlapping filters, which could cause misselection. The descriptions help but are not always enough to clearly distinguish the best tool.

    Naming Consistency2/5

    Tool names use a mix of verbs (refresh, find, get, list, search) without a consistent convention. Some are find_* (e.g., find_store, find_nearest_stores), some get_* (get_store_info, get_store_hours), some list_* (list_stores_in_area, list_store_categories), and some search_* (search_products). This mixed style makes it harder to predict tool names from intent, though the noun part is generally clear.

    Tool Count5/5

    With 12 tools covering store lookup, store details, product search, categories, promotions, and session management, the count is well-scoped for the domain. Each tool has a distinct role, and there are enough tools to represent the core API surface without being overwhelming.

    Completeness4/5

    The tool set covers the typical read-only operations for a grocery store API: finding stores, retrieving store info, searching products, filtering by category and promotion, and getting product details. Minor gaps exist (e.g., no tool for store reviews or a direct list-all-products endpoint), but the main workflows users would expect are well covered.

    Maintenance

    ActivitySlowing
    ResponsivenessUnresponsive

    Resources