rabatt.codes

Wo spare ich am meisten?

top_vouchers

Read-onlyIdempotent

Lists the currently valid vouchers and offers with the highest discounts in one country, optionally within one category (for example fashion, electronics, travel, beauty). Use it when the user asks where they can save most right now or wants current deals for a category. The result names the available categories. 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>"
    },
    "name": "top_vouchers"
  }
}

Input Schema

Name	Required	Description	Default
`country`	Yes	Country of the shopper: CH (Switzerland), DE (Germany) or AT (Austria). Required — ask the user if unknown.
`category`	No	Optional category, as a German or English word or a category slug.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 12, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds real context beyond that: results are limited to currently valid offers, the response names the available categories, and the output language is German — a non-obvious trait an agent needs before relaying results.

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

Conciseness4/5

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

Three short sentences, front-loaded with purpose and scope, then usage, then output notes; nothing is redundant. It could be marginally tighter, but no sentence is wasted.

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 two-parameter, read-only lookup with no output schema, the description covers purpose, trigger, filtering scope, and result language. It is slightly thin on result shape — how many vouchers come back, whether the list is ranked by discount — but nothing essential to calling it is missing.

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%, so both parameters are already documented, giving a baseline of 3. The description adds meaning on top by enumerating example categories (fashion, electronics, travel, beauty), which tells the agent what kinds of values the free-text category field accepts.

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?

The description gives a specific verb and resource ('Lists the currently valid vouchers and offers with the highest discounts') and scopes it to one country plus an optional category. It does not name or contrast with the sibling tools find_shop_vouchers or buy_now_or_wait, so an agent still has to infer which tool to pick from names alone.

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?

It states a clear trigger: the user asks where they can save most right now, or wants current deals for a category. There are no explicit exclusions or named alternatives, which keeps it just short of a 5.

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

All rabatt.codes tools Inspect

Try in Browser

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

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?