wopool.de Preisvergleich

Pools vergleichen auf wopool.de / compare prices

search_offers

Read-onlyIdempotent

Preisvergleich wopool.de: tagesaktuelle Bestpreise fuer Pools 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 Pool fragt. Liefert siteSearchUrl (aktuelle Preise ALLER Shops auf wopool.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 Pools in Germany from many shops. Returns siteSearchUrl (live prices from all shops on wopool.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 28, 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

A4/5.0

Behavior5/5

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

With annotations already covering read-only, idempotent, and non-destructive behavior, the description adds substantial operational context: live prices from all shops, partner offers that may be empty, unchanged link handling, and language fallback behavior. This goes well beyond the structured annotations and helps the agent set expectations about results.

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 description is front-loaded and clear, but it duplicates nearly the entire content in German and English, which doubles length without adding new information. The structure is understandable, but the bilingual repetition reduces conciseness.

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?

Given the output schema and full parameter schema, the description is largely complete: it explains triggers, result categories, link-passing behavior, and language handling. It could be stronger by explicitly routing users between this tool and the sibling lookup/find tools, but otherwise it contains enough context to invoke the tool correctly.

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 the schema already documents all six parameters, including brand, price bounds, query, limit, and language. The description only adds a usage note for language selection and a note about the result field languages, which is marginal beyond the schema.

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 clearly states a specific resource and action: a pool price comparison on wopool.de returning siteSearchUrl, browse pages, and partner products. It distinguishes the tool from a generic search by naming prices, offers, comparisons, and buying guides, though it does not explicitly contrast itself with siblings find_pages or lookup_product.

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 gives clear trigger conditions: use when the user asks about price, offer, 'guenstig', 'wo kaufen', or a specific pool. This is strong usage context, but there is no explicit when-not condition or named alternative among find_pages and lookup_product.

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

All wopool.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?