Skip to main content
Glama

Gutscheine für einen Shop

find_shop_vouchers
Read-onlyIdempotent

Looks up the currently valid voucher codes and offers for one online shop in Switzerland, Germany or Austria, using the live data of rabatt.codes (supplied directly by the shops, updated several times a day). Use it when the user asks whether a coupon, promo code or discount exists for a named shop. Returns discount, conditions and expiry date per entry, plus a link to the shop page on rabatt.codes (the code itself is shown there, not in this result). If nothing is valid right now, it says so and adds when the next promotion is expected, if known. Results are in German.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "country": "<country>",
      "shop": "<shop>"
    },
    "name": "find_shop_vouchers"
  }
}

Input Schema

NameRequiredDescriptionDefault
shopYesShop name or domain, e.g. "Zalando" or "zalando.ch".
countryYesCountry of the shopper: CH (Switzerland), DE (Germany) or AT (Austria). Required — ask the user if unknown.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Beyond the read-only/idempotent hints, it discloses data provenance and freshness ('live data of rabatt.codes, supplied directly by the shops, updated several times a day'), the exact return fields (discount, conditions, expiry date), the crucial caveat that the code itself is not in the result but linked on the shop page, and the empty-result behavior with next-promotion hint. It also states results are in German. The only wrinkle is that 'live data' from an external service sits oddly with openWorldHint=false, but that is a hint-semantics quibble rather than a description claim of a write or destructive action.

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?

Front-loaded with purpose and scope, then usage trigger, then return shape and the code-not-included caveat, then empty-state and language. Five sentences, none redundant; even the 'Results are in German' note prevents a downstream formatting mistake.

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?

No output schema exists, and the description compensates fully by enumerating the returned fields, the link-only code behavior, and the no-result case. For a two-parameter lookup tool, an agent has everything needed to call it and to explain the answer to a user.

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 coverage is 100%, with the shop example ('Zalando' or 'zalando.ch') and the country enum meanings already documented in the schema. The description adds no format or resolution guidance for the shop string (e.g. what happens with ambiguous names), so it sits at the baseline where the schema does the work.

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

Purpose4/5

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

States a specific verb ('looks up') plus a precisely scoped resource: currently valid voucher codes and offers for ONE shop, limited to CH/DE/AT, sourced from rabatt.codes. The 'one online shop' scope implicitly separates it from a list-style sibling, but no sibling is named, so the differentiation is inferred rather than explicit.

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?

'Use it when the user asks whether a coupon, promo code or discount exists for a named shop' gives a clear triggering condition, and the country enum plus 'ask the user if unknown' handles the prerequisite. It stops short of exclusions or naming which sibling to use for aggregate/wait-advice questions.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources