Skip to main content
Glama
blyatman996

tea-planner

by blyatman996
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to tea-planner

No user-submitted related servers found.

    Related Servers

    • 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
      -

    • 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
      -

    • mcp-drink-main

      niceheadwkt
      F
      license
      A
      quality
      B
      maintenance
      MCP server for 一沐日 beverage ordering, enabling users to query menus, place, list, update, delete, and analyze duplicate drink orders through natural language.
      10
      -
    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

    A4.1/5.0

    Scored across 11 tools

    Disambiguation5/5

    Each tool targets a distinct action or resource: logging, undo, inventory, history, hot recommendation, cold recommendation, add/remove/clear inventory, brewer settings, and feedback tuning. Even the closely related record and review tools are clearly separated by purpose—one logs a drink event, the other records feedback and adjusts brewing parameters.

    Naming Consistency4/5

    Most tools follow a clear lower_snake_case verb pattern like add_tea, remove_tea, clear_inventory, and set_brewer. Minor deviations exist: inventory and history are noun-style commands rather than verb_noun, and undo_record is a prefixed form, but the overall naming remains readable and predictable.

    Tool Count5/5

    With 11 tools, the server is well-scoped for a personal tea planning application. Each tool covers a distinct workflow from inventory management and drinking logs to hot/cold recommendations and brew parameter tuning, with no obvious redundancy.

    Completeness4/5

    The tool surface covers the core lifecycle: add/remove/clear/list inventory, log/undo/history drinking, recommend hot and cold brews, adjust brewer capacity, and record tasting feedback. A minor gap is the lack of a direct tea parameter editing tool, though re-adding teas and review-based tuning mitigate this.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources