Pepesto Agent-to-Cart
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.
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.
Tool Definition Quality
Average 4.9/5 across 1 of 1 tools scored.
Only one tool exists, so there is no possibility for confusion or overlap between tools.
With a single tool, naming consistency is trivially maintained. The name uses a clear verb_noun structure.
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.
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 toolpepesto_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.
| Name | Required | Description | Default |
|---|---|---|---|
| locale | No | Optional locale/region hint, e.g. 'en-CH' or 'de-DE'. | |
| shopping_list | Yes | Free-form shopping list. One item per line or comma-separated, e.g. '2 bananas\nmilk\n500g spaghetti'. |
Tool Definition Quality
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.
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.
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.
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.
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.
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.
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!
Related MCP Servers
- Flicense-qualityDmaintenanceEnables cross-store price comparison and recipe-driven cart automation for Israeli grocery stores Shufersal and Tiv Taam, with an extensible architecture for additional stores.
- Alicense-qualityDmaintenanceEnables 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.363MIT
- Alicense-qualityCmaintenanceEnables 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.1MIT
- Alicense-qualityAmaintenanceEnables 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.11589MIT