Skip to main content
Glama
niceheadwkt

mcp-drink-main

by niceheadwkt
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to mcp-drink-main

No user-submitted related servers found.

    Related Servers

    • licha-order-mcp

      lichadecha
      F
      license
      A
      quality
      B
      maintenance
      An MCP server for ordering tea from Licas Tea, allowing AI to find stores, view menus, build orders, and estimate prices in conversation. Currently read-only: no real orders or payments.
      4
      -

    • Food402

      rersozlu
      A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that enables AI assistants to order food from TGO Yemek by browsing restaurants, managing carts, and completing checkouts. It allows users to handle address selection and order tracking directly through natural language interactions.
      29 npm
      13
      MIT

    • cafe-mcp-server

      hanluOMH
      F
      license
      A
      quality
      B
      maintenance
      MCP server that recommends coffee based on preferences (mood, milk, caffeine, temperature) from a static menu; includes tools for listing menu, recommending, and explaining recommendations.
      3
      -

    • tea-planner

      blyatman996
      A
      license
      A
      quality
      B
      maintenance
      MCP server for tea enthusiasts to get daily tea recommendations, manage tea inventory, and fine-tune brewing parameters based on taste feedback.
      11
      1
      BSD 3-Clause
    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

    A3.8/5.0

    Scored across 10 tools

    Disambiguation5/5

    Each tool has a distinct purpose: listing orders, finding duplicates by name, searching all duplicates, getting duplicate statistics, updating/deleting by ID or by name, fetching the menu, and placing orders. The update and delete pairs are clearly differentiated by the identifier type (doc_id vs. name), and the duplicate tools are distinguished by scope.

    Naming Consistency4/5

    Most tools follow a verb_noun pattern (e.g., list_recent_orders, get_menu, place_drink_order), but there are minor inconsistencies such as using both 'find_' and 'search_' for similar duplicate operations, and 'update_drink_order' versus 'update_order_by_name' where the object naming varies. Overall the pattern is readable but not perfectly uniform.

    Tool Count5/5

    With 10 tools, the server is well-scoped for the drink ordering and duplicate-detection domain. Each tool serves a necessary function, and the count is neither too sparse nor overwhelming.

    Completeness5/5

    The tool surface covers the full CRUD lifecycle for orders (place, list, update, delete), includes menu retrieval, and provides comprehensive duplicate detection and statistics. No obvious gaps exist for the intended functionality.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources