wogrill.de Preisvergleich

Grills vergleichen auf wogrill.de / compare prices

search_offers

Read-onlyIdempotent

Preisvergleich wogrill.de: tagesaktuelle Bestpreise fuer Grills aus vielen Shops (u. a. Amazon, eBay), mit Filtern, Vergleichen und Kaufratgebern. Nutze dieses Tool, wenn ein Nutzer nach Preis, Angebot, "guenstig", "wo kaufen" oder einem konkreten Grill fragt. Liefert siteSearchUrl (aktuelle Preise ALLER Shops auf wogrill.de), browse (passende Vergleichsseiten, Ratgeber und Markenseiten) und products (Angebote von Partner-Shops, die eine Weitergabe erlauben – kann leer sein). Gib dem Nutzer die Links unveraendert weiter. EN: Today's best prices for Grills in Germany from many shops. Returns siteSearchUrl (live prices from all shops on wogrill.de), matching comparison pages, buying guides and brand pages (browse) and partner offers (products, may be empty). Pass links on unchanged. Set language to the user's language (e.g. "en", "tr", "fr") to get pages in that language; the result field languages lists what the site offers.

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": "search_offers"
  }
}

Input Schema

Name	Required	Description
`brand`	No	Marke / brand (exakter Wert aus facets.marke, z.B. "Nike").
`limit`	No	Maximale Anzahl Partner-Angebote (Default 24, max 100).
`query`	No	Suchbegriff / search term, z.B. Modell, Marke, Eigenschaft ("Balkonkraftwerk 800W", "iPhone 15"). Optional.
`language`	No	Sprache der Seiten-Links / language of page links (ISO 639-1, z. B. de, en, tr, ar, fr, zh). Default: Accept-Language, sonst de. Bietet die Seite die Sprache nicht an: en.
`maxPrice`	No	Hoechstpreis / max price in EUR (optional).
`minPrice`	No	Mindestpreis / min price in EUR (optional).

Output Schema

Name	Required	Description
`site`	No
`count`	Yes
`query`	No
`facets`	No	Verfuegbare Filter-Werte (Marke + domain-spezifische Attribute) mit Trefferzahlen — zum gezielten Nachfiltern via query/brand/minPrice/maxPrice.
`products`	Yes
`updatedAt`	No
`disclosure`	No
`catalogVersion`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 29, 2026

changedInput schema / properties / language / description

Previous value: -"Antwortsprache / response language (de|en). Default: Accept-Language, sonst de."New value: +"Sprache der Seiten-Links / language of page links (ISO 639-1, z. B. de, en, tr, ar, fr, zh). Default: Accept-Language, sonst de. Bietet die Seite die Sprache nicht an: en."

changedInput schema / properties / language / enum

Previous value: -[
-  "de",
-  "en"
-]New value: +[
+  "de",
+  "en",
+  "tr",
+  "ar",
+  "ru",
+  "pl",
+  "uk",
+  "fr",
+  "es",
+  "it",
+  "pt",
+  "nl",
+  "ro",
+  "el",
+  "hr",
+  "cs",
+  "hu",
+  "fa",
+  "zh",
+  "ja"
+]

Changed6 schema fields changedOct 28, 2026

changedInput schema / properties / brand / description

Previous value: -"Auf eine Marke einschraenken (exakter Wert aus facets.marke, z.B. \"Nike\")."New value: +"Marke / brand (exakter Wert aus facets.marke, z.B. \"Nike\")."

addedInput schema / properties / language

Added value: +{
+  "description": "Antwortsprache / response language (de|en). Default: Accept-Language, sonst de.",
+  "enum": [
+    "de",
+    "en"
+  ],
+  "type": "string"
+}

changedInput schema / properties / limit / description

Previous value: -"Maximale Anzahl Ergebnisse (Default 24, max 100)."New value: +"Maximale Anzahl Partner-Angebote (Default 24, max 100)."

changedInput schema / properties / maxPrice / description

Previous value: -"Hoechstpreis in EUR (optional)."New value: +"Hoechstpreis / max price in EUR (optional)."

changedInput schema / properties / minPrice / description

Previous value: -"Mindestpreis in EUR (optional)."New value: +"Mindestpreis / min price in EUR (optional)."

changedInput schema / properties / query / description

Previous value: -"Suchbegriff, z.B. Modell/Marke/Eigenschaft (\"Balkonkraftwerk 800W\", \"iPhone 15 schwarz\"). Optional."New value: +"Suchbegriff / search term, z.B. Modell, Marke, Eigenschaft (\"Balkonkraftwerk 800W\", \"iPhone 15\"). Optional."

Changed11 schema fields changedJul 7, 2026

addedInput schema / properties / brand

Added value: +{
+  "description": "Auf eine Marke einschraenken (exakter Wert aus facets.marke, z.B. \"Nike\").",
+  "type": "string"
+}

changedInput schema / properties / limit / description

Previous value: -"Maximale Anzahl Ergebnisse (Default 24, max 50)."New value: +"Maximale Anzahl Ergebnisse (Default 24, max 100)."

changedInput schema / properties / limit / maximum
```
Previous value: -50New value: +100
```

addedInput schema / properties / maxPrice

Added value: +{
+  "description": "Hoechstpreis in EUR (optional).",
+  "type": "number"
+}

addedInput schema / properties / minPrice

Added value: +{
+  "description": "Mindestpreis in EUR (optional).",
+  "type": "number"
+}

changedInput schema / properties / query / description

Previous value: -"Optionaler Suchbegriff — filtert nach Titel, Marke oder Haendler."New value: +"Suchbegriff, z.B. Modell/Marke/Eigenschaft (\"Balkonkraftwerk 800W\", \"iPhone 15 schwarz\"). Optional."

addedOutput schema / properties / facets

Added value: +{
+  "description": "Verfuegbare Filter-Werte (Marke + domain-spezifische Attribute) mit Trefferzahlen — zum gezielten Nachfiltern via query/brand/minPrice/maxPrice.",
+  "type": "array"
+}

addedOutput schema / properties / products / items / properties / attributes

Added value: +{
+  "description": "Domain-spezifische Filter-Attribute, z.B. {farbe, watt, speicher, reichweite}.",
+  "type": "object"
+}

addedOutput schema / properties / products / items / properties / brand
```
Added value: +{
+  "type": "string"
+}
```

addedOutput schema / properties / products / items / properties / detailUrl

Added value: +{
+  "description": "Zitierfaehige Produktseite mit Preisverlauf.",
+  "type": "string"
+}

addedOutput schema / properties / products / items / properties / priceStats / description
```
Added value: +"30-Tage-Preisstatistik (avg/min/max, isLowest30d)."
```

First observedJul 6, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the safety profile is covered. The description adds genuinely useful behavior beyond that: products may be empty because only partner shops permitting redistribution are included, siteSearchUrl always covers ALL shops, and language falls back to en when unsupported. Return-shape details are already in the output schema.

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

Conciseness3/5

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

The trigger condition and the three result fields are front-loaded, which is good. However, the German and English halves are near-verbatim duplicates, roughly doubling length without adding information, which is wasteful for a token-sensitive caller.

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?

With an output schema present, the description needn't document return values, and it still summarizes them. All six optional parameters are schema-documented and annotations carry safety. The only real gap is the absence of guidance on how this differs from the two sibling tools.

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 the baseline is 3. The description earns extra by explaining the language parameter's semantics (set to the user's language; the result lists which languages the site offers) and by clarifying that siteSearchUrl always reflects all shops regardless of filters, which the schema alone does not convey.

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 states a specific verb and resource: a price-comparison search for Grills on wogrill.de that returns live prices, comparison pages and partner offers. It is clearly distinguishable from find_pages and lookup_product by its price/offer framing, though it never names those siblings explicitly to draw the boundary.

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?

Explicit triggering conditions are given: use when the user asks about price, an offer, "guenstig", "wo kaufen" or a concrete Grill. It also states a hard operating constraint (pass links on unchanged) and a language-setting rule. It stops short of saying when NOT to use it versus find_pages/lookup_product.

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

All wogrill.de Preisvergleich 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?