wouhr.de Preisvergleich

Server Details

Deutscher Preisvergleich für Uhren – Bestpreis-Suche (read-only).

If you are the author of this connector, you can claim ownership by verifying the domain or GitHub account it belongs to. Claimed connector authors can inspect health checks, view analytics, and manage their listing.

Status: Healthy
Uptime: 99.9% over 42 days
Last Tested: 2026-09-28 21:32
Transport: Streamable HTTP · MCP 2025-11-25
URL

TDQS

A4.4/5.0

Scored 2026-09-23 23:10 across 2 tools

Disambiguation5/5

The two tools have clearly distinct purposes: search_offers handles broad queries across the catalog, while lookup_product targets a specific product by ID or URL. No overlap or ambiguity exists.

Naming Consistency5/5

Both tool names follow the same verb_noun snake_case pattern: lookup_product and search_offers. Consistent and predictable.

Tool Count3/5

With only 2 tools, the set feels minimal but is functional for a simple price-comparison use case. It borders on thin, so a middle score is appropriate.

Completeness4/5

The core workflows — searching for products and looking up a specific product's price details — are covered. Minor gaps exist (e.g., no bulk listing or category browsing) but the surface is adequate for the stated purpose.

Available Tools

2 tools

lookup_productProdukt auf wouhr.de per ID/URL nachschlagenA

Read-onlyIdempotent

Inspect

Schlaegt ein konkretes Produkt im aktuellen wouhr.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 wouhr.de catalog by ID (ASIN/externalId) or Amazon product URL (read-only).

ParametersJSON Schema

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

ParametersJSON 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

A4.4/5.0

Behavior5/5

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

Annotations already declare readOnlyHint and idempotentHint. The description adds that the tool is read-only and returns specific data (best price, 30-day stats, offer link). No contradictions; the description enhances transparency beyond annotations.

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?

The description is concise but includes both German and English versions, which may be redundant. Front-loads key information well. Slightly longer than necessary due to bilingual repetition, but still efficient.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the simple nature (two optional parameters but exactly one required), high schema coverage, and presence of an output schema (not shown but mentioned), the description is complete. It covers all needed aspects for agent invocation.

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% with descriptions for both parameters. The description adds clarity by stating 'exactly one of the fields id/url' and explaining the nature of each parameter (ASIN/ASIN extraction from URL). This goes beyond the schema alone.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool looks up a specific product by ID or URL, returns best price, 30-day price stats, and offer link. It distinguishes itself from the sibling tool 'search_offers' by focusing on a single product lookup.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description specifies that exactly one of 'id' or 'url' must be provided, but does not explicitly state when to use this tool versus the sibling 'search_offers' or provide exclusion criteria. The context signals mention the sibling but the description lacks direct guidance.

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

search_offersUhren in Deutschland zum Bestpreis finden (Amazon, eBay, AliExpress)A

Read-onlyIdempotent

Inspect

Findet Uhren zum guenstigsten aktuellen Preis in Deutschland (EUR) ueber Amazon, eBay und AliExpress — Preisvergleich wouhr.de. Nutze dieses Tool, wenn ein Nutzer nach Preis, Angebot, "guenstig", "wo kaufen" oder einem konkreten Uhr fragt. Durchsucht den vollen Katalog (mehrere hundert 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 Uhren across Amazon, eBay and AliExpress; returns best price, price trend, filter attributes and a direct link.

ParametersJSON Schema

Name	Required	Description
`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

ParametersJSON 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

A4.3/5.0

Behavior5/5

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

Annotations already mark the tool as read-only, idempotent, and non-destructive, and the description adds substantial behavioral context: it searches the full catalog, returns a 30-day price trend via priceStats.isLowest30d, provides domain-specific attributes, includes facets, and explicitly discloses the affiliate relationship with unchanged pricing. No contradiction 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.

Conciseness4/5

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

The German text is front-loaded with purpose, followed by usage guidance, output details, and behavioral disclosures, which is a sensible structure. It is not maximally concise because the English closing sentence largely repeats the German content, and the output field list is dense but justified.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the rich output schema and strong annotations, the description is complete enough for an agent to invoke the tool correctly: it covers the trigger condition, filtering options, returned fields, facets, and affiliate behavior. The only minor omission is the comparison with lookup_product, which is not strictly necessary for correct invocation.

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 adds meaning by explaining that results are filterable by search term, brand, and price range, and it provides example query values. The added value is moderate because the examples are inconsistent with the watch domain and the brand parameter's 'exact value from facets.marke' requirement already comes from 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 what the tool does: find the cheapest current price for watches in Germany in EUR across Amazon, eBay, and AliExpress, with a specific resource and scope. It does not explicitly differentiate itself from the sibling lookup_product, and the schema examples like 'Balkonkraftwerk 800W' and 'iPhone 15 schwarz' somewhat conflict with the watch-specific scope.

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?

The description explicitly says when to use the tool: 'Nutze dieses Tool, wenn ein Nutzer nach Preis, Angebot, "guenstig", "wo kaufen" oder einem konkreten Uhr fragt.' This is strong, concrete usage guidance. It does not, however, say when not to use it or mention lookup_product as an alternative, so it stops 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.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

2 tool updatesJul 7, 2026

Changedlookup_product5 fields changed

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)."
```

Changedsearch_offers11 fields changed

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)."
```

2 tool updatesJul 6, 2026
- First observedlookup_product
- First observedsearch_offers

Related MCP Connectors

wosneaker.de Preisvergleich A
de.wosneaker
Deutscher Preisvergleich für Sneaker – Bestpreis-Suche (read-only).
E-commerce & Retail Search
22
wohandy.de Preisvergleich A
de.wohandy
Deutscher Preisvergleich für Handys – Bestpreis-Suche (read-only).
E-commerce & Retail Search
22
woebike.de Preisvergleich A
de.woebike
Deutscher Preisvergleich für E-Bikes – Bestpreis-Suche (read-only).
E-commerce & Retail Search
22
wolaptop.de Preisvergleich A
de.wolaptop
Deutscher Preisvergleich für Laptops – Bestpreis-Suche (read-only).
E-commerce & Retail Search
22

Related MCP Servers

geizhals-mcp
E-commerce & Retail Search
Samxel
A
license
Not graded
quality
B
maintenance
Enables AI to search Geizhals price-comparison data, including products, best prices, price history, ratings, categories, and deals.
Updated 3 days ago (2026-09-26 08:50 UTC)
4
MIT
chrono24-mcp
E-commerce & Retail Web Scraping
samiashi
A
license
A
quality
A
maintenance
Enables MCP-capable clients like Claude, Codex, and Cursor to search Chrono24 watch listings, filter by price/location/seller, and retrieve detailed watch specs, photos, and dealer info directly in chat.
Updated 12 days ago (2026-09-17 10:06 UTC)
25
15 npm
1
MIT
idealo MCP Serverofficial
E-commerce & Retail Search
idealo
A
license
Not graded
quality
F
maintenance
Enables product search, price comparison, and price history analysis across 6 European marketplaces (DE, AT, GB, FR, IT, ES).
Updated 4 months ago (2026-05-20 10:01 UTC)
19
MIT
japan-market-mcp
E-commerce & Retail Web Scraping Search
atushi1841
F
license
Not graded
quality
B
maintenance
Enables AI agents to search and compare prices across Japanese used camera, watch, luxury brand, and instrument marketplaces from multiple stores, returning price, brand, condition, and source store information.
Updated 8 days ago (2026-09-20 23:30 UTC)
-