Skip to main content
Glama
Sign In
Swissgroceries MCP

Swissgroceries MCP

by nicktcode
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_promotions

Lists current promotional deals across Swiss grocery chains, filtered by chain, product keyword, store, or days until expiry to help find sales and deals ending soon.

Instructions

List current promotional deals across configured Swiss grocery chains. Filter by chain, keyword, store ID, or how many days until the promotion expires. Returns promotion name, discount, validity dates, and applicable stores. Use for "what is on sale this week?", "any Migros deals on cheese?", or "promotions ending today".

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_promotions"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryNoOptional keyword to filter promotions by product name, e.g. "Käse", "wine".
chainsNoLimit to specific chains. Omit to fetch promotions from all configured chains. Coop City (coopcity) is opt-in and only included when listed here.
storeIdsNoRestrict to promotions valid at these store IDs (chain-specific). Obtain store IDs from find_stores.
endingWithinDaysNoOnly return promotions ending within this many days (1–60). Useful for "ending soon" queries.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.12.0
    • changedInput schema / properties / chains / items / enum
      Previous value: -[
-  "migros",
-  "coop",
-  "aldi",
-  "denner",
-  "lidl",
-  "farmy",
-  "volgshop",
-  "ottos",
-  "coopcity"
-]New value: +[
+  "migros",
+  "coop",
+  "aldi",
+  "denner",
+  "lidl",
+  "volgshop",
+  "ottos",
+  "coopcity"
+]
  2. Changed2 schema fields changedv0.11.0
    • changedInput schema / properties / chains / description
      Previous value: -"Limit to specific chains. Omit to fetch promotions from all configured chains."New value: +"Limit to specific chains. Omit to fetch promotions from all configured chains. Coop City (coopcity) is opt-in and only included when listed here."
    • changedInput schema / properties / chains / items / enum
      Previous value: -[
-  "migros",
-  "coop",
-  "aldi",
-  "denner",
-  "lidl",
-  "farmy",
-  "volgshop",
-  "ottos"
-]New value: +[
+  "migros",
+  "coop",
+  "aldi",
+  "denner",
+  "lidl",
+  "farmy",
+  "volgshop",
+  "ottos",
+  "coopcity"
+]
  3. First observedv0.7.10

TDQS

A4/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full behavioral burden. 'List' clearly implies a read-only operation and the description discloses the returned fields, but it says nothing about result volumes, pagination, whether 'current' means strictly active-now, or freshness/caching of the aggregated chain data. That is a real gap for a multi-source scraper-style tool, though the core read-only nature is clear.

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?

Three sentences: purpose, filter dimensions, return shape, then example queries. The purpose is front-loaded and every clause adds routing or selection value; nothing is redundant filler.

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

Completeness4/5

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

For a read-only, four-optional-parameter lookup with no output schema, the description covers purpose, filters, and return fields, which is most of what an agent needs. It stops short of describing result-set size or ordering behavior, which would matter when combining with plan_shopping or search_products.

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

Parameters3/5

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

Schema description coverage is 100%, so all four parameters (query, chains, storeIds, endingWithinDays) are already documented in the schema, including the coopcity opt-in nuance and the find_stores pointer. The description restates the filter dimensions in its own words but adds no format or semantic detail beyond the schema, so baseline 3 applies.

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 opens with a specific verb+resource+scope: 'List current promotional deals across configured Swiss grocery chains.' It also states the return fields (name, discount, validity dates, stores), so an agent knows exactly what the tool produces. No sibling tool overlaps with promotions, so no differentiation is needed.

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

Usage Guidelines4/5

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

Three concrete example queries ('what is on sale this week?', 'any Migros deals on cheese?', 'promotions ending today') make the intended use cases unambiguous. It lacks explicit when-not guidance or direction to an alternative tool for non-promotion queries, but the positive routing signal is strong.

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

Deploy Server

Other Tools