wokonsole.de Preisvergleich
Server Details
Deutscher Preisvergleich für Spielekonsolen – Bestpreis-Suche (read-only).
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
TDQS
Scored across 2 tools
lookup_product and search_offers have clearly distinct purposes: one is for retrieving detailed info on a specific product by ID/URL, the other is for searching across catalog with filters. No overlap in functionality.
Both tools follow a consistent verb_noun snake_case pattern: lookup_product and search_offers. No mixing of styles.
With only 2 tools, the server is minimal. For a price comparison service, one might expect additional tools for comparing products or setting price alerts, but search and lookup are the core functions. The count is borderline acceptable.
The tool set covers the primary use cases of searching and looking up product details and price trends. Missing features like product comparison or price alerts are minor gaps for a focused price comparison tool.
Available Tools
2 toolslookup_productProdukt auf wokonsole.de per ID/URL nachschlagenARead-onlyIdempotentInspect
Schlaegt ein konkretes Produkt im aktuellen wokonsole.de-Katalog per Produkt-ID (Amazon-ASIN bzw. externalId aus search_offers) ODER per Amazon-Produkt-URL nach. Liefert Bestpreis, 30-Tage-Preisstatistik und den Angebots-Link. Genau eines der Felder id/url angeben. Looks up a specific product in the wokonsole.de catalog by ID (ASIN/externalId) or Amazon product URL (read-only).
| Name | Required | Description | Default |
|---|---|---|---|
| id | No | Produkt-ID: Amazon-ASIN oder externalId. | |
| url | No | Amazon-Produkt-URL (z.B. https://www.amazon.de/dp/B0ABC123DE) — die ASIN wird extrahiert. |
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 |
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint, idempotentHint, and destructiveHint. Description adds specific output details (Bestpreis, 30-Tage-Preisstatistik, Angebots-Link), which is helpful context.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two sentences in both German and English. Clear and front-loaded, though slightly repetitive due to bilingual redundancy.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given full schema coverage, output schema, and thoughtful annotations, the description covers all necessary aspects: inputs, output types, usage rule, and read-only nature.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema has 100% coverage with parameter descriptions. Description adds critical usage constraint that exactly one parameter must be provided, which is not encoded in the schema.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Clearly states the tool looks up a specific product in the wokonsole.de catalog by ID or URL, and lists outputs. Distinguishes from sibling 'search_offers' by specifying lookup vs search.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Explicitly states 'Genau eines der Felder id/url angeben' (exactly one of id/url) and marks the operation as read-only, providing clear when-to-use and constraint.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
search_offersSpielekonsolen in Deutschland zum Bestpreis finden (Amazon, eBay, AliExpress)ARead-onlyIdempotentInspect
Findet Spielekonsolen zum guenstigsten aktuellen Preis in Deutschland (EUR) ueber Amazon, eBay und AliExpress — Preisvergleich wokonsole.de. Nutze dieses Tool, wenn ein Nutzer nach Preis, Angebot, "guenstig", "wo kaufen" oder einem konkreten Spielekonsole fragt. Durchsucht ~150 Produkte, filterbar per Suchbegriff, Marke und Preisspanne. Liefert je Produkt: Titel, Bestpreis, Marke, Bild, 30-Tage-Preistrend (priceStats.isLowest30d = aktuell guenstigster Stand), domain-spezifische Attribute (attributes, z.B. Leistung/Speicher/Farbe), einen direkten Kauf-Link (url) und eine zitierfaehige Produktseite (detailUrl). Die Antwort enthaelt zusaetzlich facets (verfuegbare Filterwerte) zum Verfeinern. Read-only, Kauf beim verlinkten Haendler (Affiliate, Preis unveraendert). Finds the cheapest current price in Germany for Spielekonsolen across Amazon, eBay and AliExpress; returns best price, price trend, filter attributes and a direct link.
| Name | Required | Description | Default |
|---|---|---|---|
| brand | No | Auf eine Marke einschraenken (exakter Wert aus facets.marke, z.B. "Nike"). | |
| limit | No | Maximale Anzahl Ergebnisse (Default 24, max 100). | |
| query | No | Suchbegriff, z.B. Modell/Marke/Eigenschaft ("Balkonkraftwerk 800W", "iPhone 15 schwarz"). Optional. | |
| maxPrice | No | Hoechstpreis in EUR (optional). | |
| minPrice | No | Mindestpreis 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 |
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true and destructiveHint=false, so the agent knows it is safe. The description adds valuable behavioral info: it is a read-only affiliate search, returns a 30-day price trend, facets for refinement, and direct purchase links. No contradictions with annotations.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is front-loaded with the core purpose and usage guidance. It is bilingual, which adds some length, but every sentence adds value. Could be slightly more concise, but overall efficient.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the output schema exists, the description provides sufficient completeness: covers use case, filtering, return fields (title, best price, price trend, facets, URLs), and behavioral traits. No gaps remain.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100%, so the description does not need to fully explain parameters. It adds a bit of context (e.g., brand must be exact value from facets, query is optional) but not significantly beyond the schema. Baseline 3 is appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool finds the cheapest current price for Spielekonsolen in Germany across Amazon, eBay, and AliExpress. It specifies the resource (Spielekonsolen, price comparison) and the verb (finden / finds), distinguishing it from the sibling tool lookup_product which likely searches for product details.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description explicitly lists when to use this tool: when a user asks for price, offer, cheap, where to buy, or a specific console name. It provides concrete triggers ('guenstig', 'wo kaufen'). It does not include explicit when-not-to-use or alternatives, but the context is clear enough.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
2 tool updates
- Changed
lookup_product5 fields changed- added
Output schema / properties / facetsAdded value: +{ + "description": "Verfuegbare Filter-Werte (Marke + domain-spezifische Attribute) mit Trefferzahlen — zum gezielten Nachfiltern via query/brand/minPrice/maxPrice.", + "type": "array" +} - added
Output schema / properties / products / items / properties / attributesAdded value: +{ + "description": "Domain-spezifische Filter-Attribute, z.B. {farbe, watt, speicher, reichweite}.", + "type": "object" +} - added
Output schema / properties / products / items / properties / brandAdded value: +{ + "type": "string" +} - added
Output schema / properties / products / items / properties / detailUrlAdded value: +{ + "description": "Zitierfaehige Produktseite mit Preisverlauf.", + "type": "string" +} - added
Output schema / properties / products / items / properties / priceStats / descriptionAdded value: +"30-Tage-Preisstatistik (avg/min/max, isLowest30d)."
- Changed
search_offers11 fields changed- added
Input schema / properties / brandAdded value: +{ + "description": "Auf eine Marke einschraenken (exakter Wert aus facets.marke, z.B. \"Nike\").", + "type": "string" +} - changed
Input schema / properties / limit / descriptionPrevious value: -"Maximale Anzahl Ergebnisse (Default 24, max 50)."New value: +"Maximale Anzahl Ergebnisse (Default 24, max 100)." - changed
Input schema / properties / limit / maximumPrevious value: -50New value: +100 - added
Input schema / properties / maxPriceAdded value: +{ + "description": "Hoechstpreis in EUR (optional).", + "type": "number" +} - added
Input schema / properties / minPriceAdded value: +{ + "description": "Mindestpreis in EUR (optional).", + "type": "number" +} - changed
Input schema / properties / query / descriptionPrevious value: -"Optionaler Suchbegriff — filtert nach Titel, Marke oder Haendler."New value: +"Suchbegriff, z.B. Modell/Marke/Eigenschaft (\"Balkonkraftwerk 800W\", \"iPhone 15 schwarz\"). Optional." - added
Output schema / properties / facetsAdded value: +{ + "description": "Verfuegbare Filter-Werte (Marke + domain-spezifische Attribute) mit Trefferzahlen — zum gezielten Nachfiltern via query/brand/minPrice/maxPrice.", + "type": "array" +} - added
Output schema / properties / products / items / properties / attributesAdded value: +{ + "description": "Domain-spezifische Filter-Attribute, z.B. {farbe, watt, speicher, reichweite}.", + "type": "object" +} - added
Output schema / properties / products / items / properties / brandAdded value: +{ + "type": "string" +} - added
Output schema / properties / products / items / properties / detailUrlAdded value: +{ + "description": "Zitierfaehige Produktseite mit Preisverlauf.", + "type": "string" +} - added
Output schema / properties / products / items / properties / priceStats / descriptionAdded value: +"30-Tage-Preisstatistik (avg/min/max, isLowest30d)."
2 tool updates
- First observed
lookup_product - First observed
search_offers
Related MCP Connectors
Deutscher Preisvergleich für Tablets – Bestpreis-Suche (read-only).
Deutscher Preisvergleich für Handys – Bestpreis-Suche (read-only).
Deutscher Preisvergleich für Laptops – Bestpreis-Suche (read-only).
Deutscher Preisvergleich für Sneaker – Bestpreis-Suche (read-only).
Related MCP Servers
- AlicenseNot gradedqualityBmaintenanceEnables AI to search Geizhals price-comparison data, including products, best prices, price history, ratings, categories, and deals.2MIT
- AlicenseAqualityDmaintenanceSearches UK electronics products across multiple retailers, compares prices, and provides purchase links.2110MIT

idealo MCP Serverofficial
AlicenseNot gradedqualityFmaintenanceEnables product search, price comparison, and price history analysis across 6 European marketplaces (DE, AT, GB, FR, IT, ES).16MIT- AlicenseAqualityBmaintenanceEnables searching geizhals.de for products and retrieving shop prices and offers to assist with price comparison.2MIT