wolaptop.de Preisvergleich
Server Details
Deutscher Preisvergleich für Laptops – Bestpreis-Suche (read-only).
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
TDQS
Scored across 2 tools
The two tools have clearly distinct purposes: search_offers performs broad searches for laptops with multiple filters, while lookup_product retrieves details for a specific product by ID or URL. There is no overlap in functionality.
Both tool names follow a consistent verb_noun pattern using snake_case: 'lookup_product' and 'search_offers'. This makes the action and target immediately clear.
With only two tools, the server is minimal but functional for basic price comparison. The tools cover search and detail lookup, which is reasonable for a focused domain, though additional tools like category listing or price history could enhance completeness.
The server covers the essential workflows: finding products by search and retrieving detailed price info for a specific product. Minor gaps like lacking a tool to compare multiple products or view trending items, but core operations are present.
Available Tools
2 toolslookup_productProdukt auf wolaptop.de per ID/URL nachschlagenARead-onlyIdempotentInspect
Schlaegt ein konkretes Produkt im aktuellen wolaptop.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 wolaptop.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. The description adds that the operation is read-only and mentions returned data (best price, 30-day stats, offer link), which is consistent and adds value.
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 somewhat lengthy due to bilingual text (German and English), but the key information is front-loaded and each sentence adds value. Could be slightly more concise.
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 presence of an output schema and annotations, the description captures essential behavioral and usage details. It covers what the tool does, its inputs, and outputs, making it complete for a simple lookup tool.
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?
The schema already describes both parameters (id and url). The description adds that exactly one field must be used and explains that externalId comes from search_offers, enhancing understanding beyond schema definitions.
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 specifies the tool looks up a product by ID or Amazon URL, and distinguishes it from the sibling tool 'search_offers' which is likely a broader search. The verb 'look up' and resource 'product' are explicit.
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 states that exactly one of 'id' or 'url' must be provided, which is a clear usage rule. However, it does not explicitly say when to use this tool over the sibling 'search_offers' or mention exclusions, though the context implies it.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
search_offersLaptops in Deutschland zum Bestpreis finden (Amazon, eBay, AliExpress)ARead-onlyIdempotentInspect
Findet Laptops zum guenstigsten aktuellen Preis in Deutschland (EUR) ueber Amazon, eBay und AliExpress — Preisvergleich wolaptop.de. Nutze dieses Tool, wenn ein Nutzer nach Preis, Angebot, "guenstig", "wo kaufen" oder einem konkreten Laptop 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 Laptops 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 and idempotentHint true. The description adds context about searching ~150 products, filtering capabilities, return fields (title, best price, brand, price trend, attributes, links), and the read-only affiliate nature. This goes beyond annotations by explaining scope and output structure.
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 informative but includes both German and English versions, making it longer than necessary. It is front-loaded with purpose and usage guidance, but the bilingual repetition reduces conciseness. Could be tightened to a single language.
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 existence of an output schema, the description does not need to detail return values. It covers parameters, usage guidance, data sources, and constraints. The tool is well-contextualized for a search tool with comprehensive filtering details.
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% with detailed parameter descriptions. The description adds only a high-level summary ('filterbar per Suchbegriff, Marke und Preisspanne'), which does not provide new meaning beyond the schema. Baseline score 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 explicitly states it finds the cheapest Laptops in Germany across Amazon, eBay, and AliExpress. It clearly distinguishes from the sibling 'lookup_product' by focusing on searching multiple offers with filtering. The verb 'search' is specific and resource 'offers' is well-defined.
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 provides explicit when-to-use scenarios: when a user asks for price, offer, 'cheap', 'where to buy', or a specific laptop. However, it does not mention when not to use or explicitly contrast with the sibling tool, leaving some ambiguity.
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 Handys – Bestpreis-Suche (read-only).
Deutscher Preisvergleich für Tablets – Bestpreis-Suche (read-only).
Deutscher Preisvergleich für Spielekonsolen – Bestpreis-Suche (read-only).
Deutscher Preisvergleich für E-Bikes – 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
- AlicenseAqualityBmaintenanceEnables searching geizhals.de for products and retrieving shop prices and offers to assist with price comparison.2MIT

idealo MCP Serverofficial
AlicenseNot gradedqualityFmaintenanceEnables product search, price comparison, and price history analysis across 6 European marketplaces (DE, AT, GB, FR, IT, ES).16MIT