Skip to main content
Glama
olgasafonova

TilbudsTrolden

by olgasafonova
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to TilbudsTrolden

No user-submitted related servers found.

    Related Servers

    • kundeavis-mcp

      donadelicc
      A
      license
      A
      quality
      C
      maintenance
      MCP server that queries Norwegian grocery store flyers (kundeaviser) to help AI agents plan cheap meals based on current offers.
      7
      MIT

    • willys-mcp

      oscarthroedsson
      A
      license
      B
      quality
      C
      maintenance
      An MCP server for Willy:s that enables recipe-based shopping cart planning, product search, price comparison, and cart management through natural language. It maps the grocery store's internal endpoints and exposes tools to manage recipes, search products, compare prices, and sync the cart.
      31
      2
      MIT

    • Swissgroceries MCP

      nicktcode
      A
      license
      A
      quality
      B
      maintenance
      A Model Context Protocol server for real-time Swiss grocery shopping that searches and compares products across 8 major Swiss retailers (Migros, Coop, Aldi, Denner, Lidl, Farmy, Volgshop, Otto’s), normalizes per-unit prices, surfaces promotions, computes optimal multi-store shopping plans, and works with any MCP-compatible client without API keys or accounts.
      2
      7
      107 npm
      35
      AGPL 3.0

    • mealplan-mcp

      evcraddock
      A
      license
      B
      quality
      D
      maintenance
      MCP server for meal planning and grocery list generation, enabling recipe storage, meal plan creation, and automated grocery lists with ignored ingredients.
      8
      2
      MIT
    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 18 tools

    Disambiguation4/5

    The descriptions include explicit USE WHEN / NOT FOR clauses that sharply delineate most tools, and the three deal tools (search_deals, get_store_offers, deals_this_week) have genuinely distinct scopes. The only real overlap is between score_recipes, generate_shopping_list, and plan_and_shop, since plan_and_shop composes the other two; an agent could still waffle on whether to chain them or call the combined entry point.

    Naming Consistency5/5

    Nearly every tool follows a clean snake_case verb_noun pattern (get_household, update_pantry, add_recipe, log_meal, generate_shopping_list). The few non-verb-led names (deals_this_week, plan_and_shop) are still readable and stylistically consistent snake_case.

    Tool Count4/5

    18 tools is on the heavier side but is justified by the broad domain spanning deals, household config, pantry, recipes, meal logging, spend tracking, and planning. Each tool maps to a distinct operation rather than being redundant filler.

    Completeness4/5

    Coverage is strong: full lifecycle for recipes (get/add/remove), pantry (get/update), household (get/update), meal and spend logging (log/get), plus deal discovery and two planning entry points. Minor gaps exist (e.g. no dedicated single-recipe fetch or granular pantry item delete), but update/overwrite semantics largely cover them.

    Maintenance

    ActivityActive
    ResponsivenessResponsive

    Resources