Skip to main content
Glama

Server Details

Turn any shopping list into a ready-to-checkout grocery cart across 26 European supermarkets.

Status
Healthy
Last Tested
Transport
Streamable HTTP
URL

Glama MCP Gateway

Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.

MCP client
Glama
MCP server

Full call logging

Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.

Tool access control

Enable or disable individual tools per connector, so you decide what your agents can and cannot do.

Managed credentials

Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.

Usage analytics

See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.

100% free. Your data is private.
Tool DescriptionsA

Average 4.9/5 across 1 of 1 tools scored.

Server CoherenceA
Disambiguation5/5

Only one tool exists, so there is no possibility for confusion or overlap between tools.

Naming Consistency5/5

With a single tool, naming consistency is trivially maintained. The name uses a clear verb_noun structure.

Tool Count3/5

A single tool for the specific purpose of creating a cart link is functional, but it feels thin for a server scope. Typically 3-15 tools are expected for good coherence.

Completeness5/5

The server's purpose is to convert a shopping list into a cart link, and the single tool fully covers this operation with no obvious missing functionality.

Available Tools

1 tool
pepesto_create_cartPepesto Agent-to-CartAInspect

Turn a free-form shopping list into a ready-to-open Pepesto cart link.

This tool is FREE and needs NO API key or authentication. Nothing is matched or charged when you call it: matching products and pricing happen LAZILY only after the USER opens the returned link in the Pepesto app, and the USER pays at checkout in the app — never here, never you.

Covers 26 European supermarkets. The response is a single block of Markdown that already contains a labeled, tappable link. Clients should surface that Markdown link AS-IS (render the link) and must NOT show the raw URL or rewrite the caption.

ParametersJSON Schema
NameRequiredDescriptionDefault
localeNoOptional locale/region hint, e.g. 'en-CH' or 'de-DE'.
shopping_listYesFree-form shopping list. One item per line or comma-separated, e.g. '2 bananas\nmilk\n500g spaghetti'.
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Despite no annotations, the description thoroughly discloses behavior: no matching or charging at call time, lazy processing only after user opens link, free usage, no auth required. Also describes response format (Markdown with labeled link). Fully transparent.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Concise yet comprehensive. First sentence states purpose, followed by bullet points with key usage notes. No redundant sentences, every line adds value. Well-structured for quick comprehension.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given no annotations and no output schema, the description covers all essential aspects: input format, output format, behavioral safety (no charges, no auth), and geographic scope. Complete for an AI agent to select and invoke the tool correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% with descriptions for both parameters. The description adds value by giving examples for shopping_list (e.g., '2 bananas\nmilk') and locale (e.g., 'en-CH'), which clarifies usage beyond the schema definitions. Not a 5 because schema already covers basics well.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action: turning a free-form shopping list into a Pepesto cart link. It specifies input, output, and context (European supermarkets, no auth). Distinguishes itself from potential alternatives by emphasizing the lazy matching and pricing, making purpose unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly says when to use (free-form shopping list), what not to worry about (no API key, no immediate charges), and how to handle the response (surface Markdown link as-is, avoid showing raw URL or rewriting caption). Provides clear context for usage without references to siblings, but self-contained.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Discussions

No comments yet. Be the first to start the discussion!

Related MCP Servers

  • F
    license
    -
    quality
    D
    maintenance
    Enables cross-store price comparison and recipe-driven cart automation for Israeli grocery stores Shufersal and Tiv Taam, with an extensible architecture for additional stores.
  • A
    license
    -
    quality
    D
    maintenance
    Enables AI assistants to interact with Rohlik Group's online grocery delivery services across multiple European countries, supporting product search, shopping cart management, order history analysis, and personalized meal suggestions based on purchase patterns.
    36
    3
    MIT
  • A
    license
    -
    quality
    C
    maintenance
    Enables personalized Mercadona grocery orders via natural language, with Nutri-Score prioritization and supervised cart execution (no payment). Supports user intake, product search, and integration with external menu systems.
    1
    MIT
  • A
    license
    -
    quality
    A
    maintenance
    Enables AI assistants to interact with Picnic online supermarket for grocery shopping, meal planning, cart management, delivery tracking, and budget-conscious shopping in Netherlands and Germany.
    115
    89
    MIT

View all MCP Servers

Try in Browser

Your Connectors

Sign in to create a connector for this server.

Resources