Skip to main content
Glama

Related Servers

Alternatives to Errand Runs MCP Server

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables local shopping research by reading the products, SKUs, stores, reviews and images actually loaded in a logged-in Chrome session, supporting product search and filtering, exact SKU selection and comparison, in-store and store research, favorites management, and authorized single-send merchant inquiries with reply retrieval. Runs entirely on the local machine with traceable research records, and is also exposed via CLI and a local web entry.
      MIT
    • F
      license
      A
      quality
      D
      maintenance
      Enables tracking personal expenses by adding, listing, deleting, and summarizing expenses by day or month, stored locally in a JSON file.
      4
      -

    TDQS

    A3.8/5.0

    Scored across 6 tools

    Disambiguation4/5

    Each tool has a fairly distinct role: logging (log_item), aggregate views (tally), planning (plan_run), closure (mark_bought), historical query (receipt), and filtered listing (list_items). The only mild overlap is between tally and list_items, both read views, but their descriptions clearly differentiate grouped-by-store counts from item-level status filtering.

    Naming Consistency4/5

    Four tools follow a clean verb_noun or verb_object pattern (log_item, list_items, mark_bought, plan_run). The remaining two (tally, receipt) are bare/single-word names, which is a minor deviation but still readable and semantically apt.

    Tool Count5/5

    Six tools is a tight, well-scoped surface for a personal errand-planning server. Every tool maps to a distinct stage of the workflow (log, review, plan, close, report, audit) with no filler.

    Completeness3/5

    The lifecycle of logging, planning, closing, and reporting is covered, but there is no way to update an item (fix quantity, retag a store) or delete/undo a mistakenly logged entry or purchase. These are notable gaps that would force workarounds for common corrections.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues